3 ms·
Frameworks are like crack. At first they make things feel great and quick and easy, but eventually the framework forces you to work around it and adds layers of
by api 16y ago
Frameworks are like crack. At first they make things feel great and quick and easy, but eventually the framework forces you to work around it and adds layers of complexity. It invades your application and forces you to do elaborate dances when you need to do something a bit differently than the framework thinks you should do it. Eventually you wind up spending more time fighting the framework than writing your app.
Rails, .NET, various J2EE bloatware, etc. are all things that I've seen the same pattern with.
Eventually I realized that there was no such thing, really, as a good vs. a bad framework. All frameworks are bad frameworks. I realized that I should spend no time looking for a framework for the same reason that I should spend no time looking for a disease.
Instead of frameworks, we need better and richer platforms with better and richer libraries, support for a variety of good languages, etc.
- misterbwong 16y agoInstead of frameworks, we need better and richer platforms with better and richer libraries, support for a variety of good languages, etc. Seems like this is what .NET and the JVM are trying to achieve. MS is putting up a lot of different languages (C#, VB, IronPython, IronRuby, etc) and the JVM is experiencing somewhat of a rebirth with languages like clojure and scala (not to mention good ol' boring java).
- api 16y agoI was referring to things like ADO.NET, event driven control data bindings, etc.