2 ms·
There used to be a fashion in some parts [1] that rather than building an application to do X you would build a framework for applications of that type. Of cou
by arethuza 12y ago
There used to be a fashion in some parts [1] that rather than building an application to do X you would build a framework for applications of that type.
Of course, the vast majority of these in-house application frameworks ended up being used for precisely one application or are overtaken by frameworks that succeed in the wider market.
1. Particularly the enterprise Java world in the bad old days.
- userbinator 12y agorather than building an application to do X you would build a framework for applications of that type. ...and then someone comes up with the idea of building a framework for building frameworks to do X: http://discuss.joelonsoftware.com/default.asp?joel.3.219431.12& http://discuss.joelonsoftware.com/default.asp?joel.3.219431....
- arethuza 12y agoIndeed, I managed to control myself by not posting that link as it sometimes upsets people. NB I did comment on that thread on Joel On Software.... :-)
- collyw 12y agoThat's kind of how we were encouraged to code (I was learning during the dot.com boom, when Java was all popular). I think the difference now is that some high quality fairly generic framework have emerged (there was nothing like Rails or Django back in 2000 as far as I am aware). Why build that part when someone else has done the hard work for you? Its well tested, documented, and there is a large knowledge base out there. (I dislike it when I hear about in house frameworks when I am in a job interview, as those will generally not be as well documented, and only a few "in house rockstars" will really understand them).