By bloid
via javabeans.asia
Published: Nov 16 2008 / 13:48
I think first as a developer, one must understand the pros and cons of the framework, and how will it affect the performance of the application to be designed. The developer must have clear idea about what is he trying to achieve by using a particular framework in his application, and whether the framework is going to give him the desired result.
-
jQuery Mask Plugin - A jQuery Plugin To Easily Implement Field Masks
-
"We tried time-limited trial. This is why we changed to feature-limited instead."
-
Mojito - Yahoo's NodeJS based Multi Device Application Framework
-
Google Analytics' Open Secret
-
A primer on PHP exceptions
-
FREE Adobe CS6 eBooks — Download 1,022 Pages of New Tutorials
Comments
rv49649 replied ago:
For the frameworks that support annotations (Spring, JUnit, EJB3, Hibernate, etc.), it has been a new revolution for reaping their advantages without nearly as much boilerplate as in the past.
I've been doing training tutorials recently where I bring folks into Java programming by writing JUnit test involving the use of Spring, iBATIS, JUnit. We start out the old fashioned way (no annotations). Then we shift gears and start using annotations. The lines of code plummet. We're then down to just writing test code. JUnit and Spring harmonize together in such a way that the programmers get to really just concentrate on what they need to accomplish. It's been a delightful experience to see folks experience this transition as they're starting out as fledgling Java programmers. (They're background is PL/SQL so they really like using iBATIS with Java too.)
zynasis replied ago:
this article is terrible. it tells us NOTHING
sashka12345 replied ago:
This article is NOT suppose to tell anything. It is merely asking a readers' opinion
Voters For This Link (11)
Voters Against This Link (16)