No i’m not talking about frameworks that addresses their own unique business needs. I’m talking about your ORMs, MVC web frameworks, javascript (including ajax) frameworks, but for now i’m talking about your everyday java enterprise application. There is at least one of this monstrocities that is being build in every big company under the pretense of “We don’t need the other stuff that framework X offers”, or maybe you’ve heard of the priceless line “Framework X contains so much features that it can affect the scalability of our enterprise application”. So with those ammunition, management will give them a go signal to build their very own abomination; maybe 2 years down the line some moron will pick up a business magazine seeing those new fangled application servers and will decide that they have to migrate to it to keep up with the trend, and yes, you’ve guess it… their framework is not compatible with the new application server and they will have to spend several thousand dollars to port it. Standards and open source frameworks exists for a reason.
-
Recent Posts
Blogroll
Archives
3 Comments
The same could be said for every new non-standard open source web framework. Do we need another one? OS developers seem to have no problem making the same decisions.
Your solution (leaving side standards) looks like the problem itself.
It frustrating but unfortunately there is no known cure - developers will develop (and not necessarily what they should be doing).
Having consulted at several Fortune 500 companies I can unequivocally state that this simply isn’t the case: every single one of those companies is using a standard, off-the-shelf web framework, ORM, JavaScript, etc. framework simply because it’s far more cost-effective on many levels.
@Caligula
Most of my experience is similar, but i’ve encountered a couple of big companies which warranted this rant because their solution was really absurd.