By bloid
via postal-code.com
Published: Jul 30 2008 / 18:31
As a collective industry we’ve been building web apps for about fifteen years now. In many ways we’ve greatly improved our development processes, our tools, our methodologies and our expectations. Today we whip out Rails apps in days that would have taken months before; single developers are producing entire commercial sites where once a team would’ve been required.
Comments
senfo replied ago:
Most of the points are fine, but the point about building atop an open-source framework shows a biased opinion. There are definitely places where an open source framework are ideal, but that doesn't mean that there aren't opportunities where a a more closed-source solution isn't better.
willcode4beer replied ago:
should read "atop *a* framework..."
However, care should be taken when using a closed source framework. Likelyhood of not being dropped (talking to you Oracle and HP) should be big. Of course, with open source, you should also make sure there is a good likelyhood of continuous development....
Shooshpanchick replied ago:
I think it's specifically mentioned that the framework must be open source because most closed-source frameworks are badly designed and badly supported/documented. Also, they have smaller user base and that's why you are less likely to receive help. In my career I've never seen a proprietary framework that was clearly documented and in most cases I have had to decompile it at some point to understand why it doesn't work as I expect.
Voters For This Link (9)
Voters Against This Link (6)