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.
Notice how I said that Rails 3 is finally a framework that I like.
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.
> 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.
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 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.