Showing posts with label web frameworks. Show all posts
Showing posts with label web frameworks. Show all posts

Friday, February 15, 2013

Giles Bowkett: Rails Went Off The Rails

It's fascinating to read Giles Bowkett on Rails, its bloat, its falling out of fashion.

Fascinating mainly because it so clearly highlights that no-one is immune from this life-cycle that goes :

  • new, simpler and easier than anything else
  • hot-new thing that everyone loves
  • adding more fluff to deal with more edge-cases
  • build-up of technical debt
  • re-writes to try to make more general, more principled, but requiring more configuration
  • old and bloated.
Certainly Python isn't immune. We've been through this cycle with Zope, Plone ... feels like Django has too. Java went through it several times. The node/js/coffeescript frameworks will go through it too. 

DOS/Windows did it. I guess the Macintosh OS has, though Apple have been more willing to kill and reboot its operating systems with the moves to OSX (BSD) and then iOS.





Friday, May 11, 2012

Meteor

Just looking at the quickstart demo of Meteor, the hot new web framework people seem to be getting excited about.

First thought. Seems to me that far more important than using the same language for the client and server is being able to write the client and server code in the same file.

That is something I've been waiting for for a long time.

Friday, February 24, 2012

Rails Off The Rails

Seems like the same thing has happened with Ruby on Rails as happened with, say, Zope.

Giles does a pretty good analysis. The key point is that as frameworks mature they start supporting legacy users and applications who, in turn, have different requirements and values from those looking for a quick way to build new applications.


Wednesday, July 13, 2011