Book Review: Design Recipes for FPGAs

Design Recipes for FPGAs is a sort of "something about everything" book. The book just lists the FPGA-related issues and doesn't cover any of those in detail. Even if there are some kind of examples - I wouldn't recommend this book to anyone. Istead, The Design Warrior's Guide to FPGAs is a much better alternative.

Book Review: The Design Warrior's Guide to FPGAs

The Design Warrior's Guide to FPGAs is a must-read book! Written in an entertaining style, the books is very interesting to read. The book provides an insightful overview of the FPGA technology, design tools and flows. This is a great book for someone that is getting started in FPGAs. After reading this book one will have the basic knowledge about FPGA technology.

Book Review: Mastering Enterprise JavaBeans 3.0

Another book about EJB 3.0 is Mastering Enterprise JavaBeans 3.0. The book focuses on the changes made since EJB 2.1. Here are some week aspects of this book:

• it is not that smoothly readable as the previous EJB book


• the book spends too much on high-level introduction of EJB 3.0 specification while it could dive into more practical details ASAP


• JPA is poorly covered

But nevertheless, the book is somewhat a good complementary material for learning EJB 3.0.

Book Review: EJB 3 in Action

EJB 3 in Action was really enjoyable to read. This is a well-structured book and covers just what is really required for Java 5 EE application development. In my opinion it is not the best suited for a beginner: it is easier to understand the text if one already has some experience with EJB 2.0. The book provides practical code examples, best practices, design patterns, and performance tuning tips.
I would strongly recommend this book to anyone who would like to get familiar with EJB 3.0.

P.S. The relevance to the JEE development is out of the scope here :) Personally, I would rather go Spring/Hibernate than JSR220 and JSR291 rather than JSR277.

P.S.2 Why not to assume that Hibernate and Spring are the de jure standards for JEE middleware development, instead of creating EJB 3.0? Political reasons? I think that Sun is still reinventing the wheel with its own "standards" and not making use of the community process.