Comment Re:WTF is "infrastructure code"? (Score 1) 153
Lets face it the technology moves quickly. So one way or the other if the code isn't updated to be current with these standards it is outdated anyway. These technology evolution is a large part of the reason frameworks evolve quickly too. At a recent Gartner IT/Symposium, they said frameworks are 90% iterative.
So yes they do move quickly. And without them you'd be doing it youself. And what you can't replicate is the 1000s of developers using it in real environments and it evolving based on what works and what doesn't. You are going to find out the hard way.
Why Use frameworks? J2EE frameworks enable a level of abstraction from the business logic. This clear separation enables the features of the application to evolve separately from the framework. You get to focus on your application instead! And once you have developed more than one application the benefits of a common framework across your applications is much greater.
Most people who develop their own end up with emeshed architecture code in their business logic which results in higher maintenance burden!
Gartner says frameworks are part of the productivity layer and recommend their client to use frameworks. As frameworks offer tighter integration with IDEs, code generators, wizards and the like you will find their adoption widespread. Have a look at www.mvc2frameworks.org for more information about mvc based frameworks and a comparison spreadsheet.
IMO being Struts based for example is a good sense for sales since it has become a defacto standard.
So yes they do move quickly. And without them you'd be doing it youself. And what you can't replicate is the 1000s of developers using it in real environments and it evolving based on what works and what doesn't. You are going to find out the hard way.
Why Use frameworks? J2EE frameworks enable a level of abstraction from the business logic. This clear separation enables the features of the application to evolve separately from the framework. You get to focus on your application instead! And once you have developed more than one application the benefits of a common framework across your applications is much greater.
Most people who develop their own end up with emeshed architecture code in their business logic which results in higher maintenance burden!
Gartner says frameworks are part of the productivity layer and recommend their client to use frameworks. As frameworks offer tighter integration with IDEs, code generators, wizards and the like you will find their adoption widespread. Have a look at www.mvc2frameworks.org for more information about mvc based frameworks and a comparison spreadsheet.
IMO being Struts based for example is a good sense for sales since it has become a defacto standard.
