If you are like this, you'll probably like Knuth's "My advice to young people", http://www.webofstories.com/play/17152. The relevant part:
And I think one of the things that I would, that would sort of come first to me is this idea of, don't just believe that because something is trendy, that it's good. I'd probably go the other extreme where if something, if I find too many people adopting a certain idea I'd probably think it's wrong or if, you know, if my work had become too popular I'd probably think I'd have to change.
How about we just use the tools that allow us to both do a good job and enjoy doing it.
If part of your enjoyment comes from feeling that you're using the optimal modern configuration, that's great. If part of your enjoyment comes from blazing trails with exciting new technology, go for it! If part of your enjoyment comes from using familiar tools in the way you feel most comfortable, that is also sweet.
In all likelihood, when you're building a compelling and performant web application, they will each serve more than adequately.
The idea that "If my work had become too popular I'd probably think I'd have to change" is terribly cynical.
Not really. For some people, the goal is to do useful work that only you can do. When your work becomes mainstream, that means there are people willing to take it and run with it. At that point, you've made a great contribution. Leave it to the next generation and move onto the next project. It keeps you from being complacent, keeps you moving forward and creating new things.
Case in point - how many new things has Steve Jobs created since he re-joined Apple? How many new things has Linus made since he started Linux? Two very different approaches to projects and work, yet I wouldn't call either of them cynical.
I don't know. I liked the rails 5 minutes blog demo. I wasn't into rails from the beginning - I followed the recent one http://guides.rubyonrails.org/getting_started.html
I think it's the ideal example for demonstrating a web framework.
1. It gives basic introduction to the framework and installation notes.
2. It's simple enough to follow, yet large enough to show major aspects of development with rails.
3. It shows all major aspects of the web application development - db access layers, db creation and migration, models and validation, request routing, controllers, views, partials...
> What impresses me is code-reuse, modularity and readability. Which is why I preferred Django instead of Rails 2.
I use both Django and Rails. Rails has various stuff which I need for a basic app out of the box, which Django doesn't have - asset pipelines, coffeescript integration, swappable templates, bundler for dependencies, rvm(not exactly rails) for isolating ruby version and gemset, tested gems for basic tasks(kaminari, devise, paperclip) etc.
I know I can do all of it in Django/Python(pip, virtualenv, coffee --watch, webassets etc etc), but rails sets up things for me and I can begin coding.
Rails does require more peripheral knowledge, but it's optimized for people who know rails. Beginners will be more at home with Django, but you are a beginner for a very short period of time, and optimizing for beginners while forfeiting comfort for people who are on-board isn't a good compromise IMO.
In an ideal world, we can have frameworks which is both beginner and power-user friendly, but I seldom see it happening it in the real world.
As far as reading code goes, I have trouble following Rails code, and my only friend is the interactive debugger - I set breakpoints, read code in the editor, continue, break...
I haven't read Django's code in a while, but it used to be quite heavy on magic - not sure about the current status.
Also, Django may not be as feature rich, but it does have the Python ecosystem, which is more comprehensive as a result of being used in academic environments.
Those times are over, fortunately. Whenever I encounter a lower-level problem I tend to look through the code rather than the documentation, because it's usually much easier to find what you're looking for.
I started a new project a few months ago and spent a day almost agonizing over 'the new hotness'. I talked with a friend about doing it the 'old way' (Rails mvc) or the 'new way' (backbone, node, etc). In the end, I just wanted to get my work done, so I chose the 'old way'. I don't see anything wrong with this. I feel like I'm still creating, I love getting up every morning and making progress on the app.
At some point, I'll probably go back and revisit. Maybe start sprinkling in some new hot here and there. The one thing that DHH has said that's really stuck with me is (paraphrasing): "Love the tools you're working with". So, I leave it at that.
The Rails use case was always truly limited. I still don't know any application that achieved maturity and stayed coded in Rails. For a while that was Twitter, but then they started moving stuff over the jvm.
Node will probably end up in a similar way, because at the end of the day no one wants to manage thousands of lines of Javascript (or any other language that doesn't enjoy the benefits of a statically typed ide).
2) That said, Javascript isn't going away. We will all be managing thousands of lines of Javascript because… that's where applications are going - client side. Good luck convincing all the browser vendors to swap.
Anyhow, I know you're just trolling but you have to up your troll game - 98% of apps fall in between "toy demo" and "twitter".
Like, that you've actually experienced and said "You know, I'm not saying this just because I'm not used to it. This bit right here is a design flaw".
This is such a tired and boring argument by this point, but I'm willing to entertain it because duck typing is at the bottom of my list of worries.
I don't think you really believe a web development framework and a feature rich blogging product were actual competitors but are simply creating strawmen to support your view. Drop the crap.
However, let me provide a counter-point ... I think that Rails 3 is finally a good framework that I want to use. Blogs written in 5 minutes (which you can still do in Rails 3) have never impressed me.
What impresses me is code-reuse, modularity and readability. Which is why I preferred Django instead of Rails 2. The biggest reason was that I can read Django's source-code, but Rails (prior to 3) was really awful in that regard and cargo-culting is OK, but only when you're starting out.
Node & Coffeescript are indeed cool and have their place. However I prefer mature frameworks that save me effort when building yet-another-admin or yet-another-facebook-login.
Not pursuing hotness is the new hotness IMHO.