By jsugrue
via java.dzone.com
Published: Mar 09 2010 / 11:18
Someone recently asked me what technologies I would recommend for the next Enterprise Web Project. Like a good little software developer, my initial reaction was "I would have to see the requirements first". And of course that is true. As much as possible I try to fight the tendency to fit requirements around the technology, because I know that I am wont to be enamoured by the latest shiny thing in the software world.
-
Design a 404 Page That Keeps Visitors On Your Site
-
The path-searching algorithm is not a backtracking algorithm
-
Deploying My Django Application to DotCloud
-
Presentation Smells
-
Orman Clark’s Vertical Navigation Menu: The CSS3 Version
-
SQL SERVER – INNER JOIN Returning More Records than Exists in Table
Comments
MCII replied ago:
Spring and Hibernate are main contributors to proverbial Java Enterprise bloatware. Nowadays you can easily avoid Spring: the DI-hype is over, the company is sold and less aggressive in the Marketing field. Moreover, now that JEE 3.1 is established finding good arguments for the proprietary Spring frameworks is more difficult than ever. Hibernate can be 'avoided', too. It's now standardized as JPA, for better or for worse.
sakuraba replied ago:
So you avoid "enterprise bloatware" by moving from Spring to EJB and from Hibernate to JPA?
That is like becoming a new athlete by switching from soccer to european football.
,
Voters For This Link (15)
Voters Against This Link (1)