Recently I came across a web application that had just two JSP pages.
What does it do? It takes a value from the user and displays his points based on the value.
And can you guess the number of back-end files used to help this process?
There were 23 packages, more than 250 java files, 13 properties files and a lot of XML files, in addition to the standard class/jar library files used in the project. Believe me, I am talking about a complete application that does not expect any dramatic enhancement in the future.
Don’t tell me that it is all about the Framework. That is what you call bad design. Especially when you can write world-class applications in 579 lines of code.
Use Struts or MVC or Spring or Ruby on Rails or anything you like in your application. Before that try using a little common sense.
Absolutely, I wonder that for even those enterprise apps that make extensive use of frameworks whether they get any real benefit out of them.
What’s the point in making something re-usable if you’re never going to re-use it?
And if you don’t follow it through ALL THE WAY (unit testing, mocking, documentation etc) then chances are it’s costing you more to develop, and you’re never going to get the payback you should.
Duncan,
Exactly what I was trying to say. As you pointed out, many enterprise solutions use these big frameworks simply for the sake of it.
Your 579 argument is flawed. It was more like 579 lines of Ruby /plus Rails/.
Very good point, developers for some reason is not happy buying a part, they HAVE to buy the whole damn car.
Use only what you need, even when it comes to frameworks.