Yes, you can `sudo gem install rails && rails new blog`.
But that's not going to get you a suitable environment for any standard Rails project today. Especially not if it involves other people.
Installing things from gists using cURL, RVM, 1.9 (Lion still comes with 1.8), juggling gem updates, bundler, cloning git repos (submodules for plugins, etc.), etc., are all totally par for the course.
rvm: managing ruby versions. This is a big win, and you offer no better way to do this.
bundler: managing dependencies. This is a big win, and you offer no better way to do this.
I'm not saying the Ruby ecosystem is perfect, but a lot of the problems are engrained in Ruby culture. Losing the problems will likely mean losing some of benefits of that culture along the way.
Why?
Seriously, even in Java you can get to "Hello World" with just a text editor. You don't need to download Eclipse first.
If installing XCode and editing things freaks you out, then you may not be cut out for the level of coding required to actually use Rails
I love the idea that someone who prefers emacs or vim over an IDE like XCode is insufficiently l33t for the awesomeness that is Rails.
And why do I need a C compiler to work in Ruby, anyway? I assume it's to compile your own version of Ruby. (Which is another way the Java comparison doesn't work -- you need the Java tools to compile your own code, not to compile Java.) But why on earth would a newbie want/need to do that?
And why do I need a C compiler to work in Ruby, anyway?
I'm not a Ruby programmer, but I'm betting it's the same reason as in Python: to be able to use libraries that have pieces written in C for speed.If your project gets up to very large scale things are probably different, but there's no need to deal with that in a "Hello World"-type tutorial.
Actually, django is worse if this tutorial is correct.
http://programmingzen.com/2007/12/22/how-to-install-django-w...
They are telling you to install a binary precompiled library. I much prefer having my dependencies managed as they are in bundler than downloading libraries manually and installing them.
I know there's been some bad blood between the Ruby and Debian communities about Debian package maintainers not accepting bleeding-edge versions of Ruby software into the Debian repos; that may have been why Ruby went off and built its own set of package managers.
1. I develop on a mac and deploy on different linux distros. It makes more sense for me to have a single system for managing ruby dependencies than to do it with 3 or 4 different systems that work differently and may not be fully compatible. Plus, with bundler and rubygems I'm not stuck on whatever version the distro decides to support.
2. If I install something like the mysql driver manually or with apt-get, and then a year from now I'm no longer around and some other developer checks out the code ... how do they know which versions of the libraries were used? With bundler all versions of all gems are checked into version control. This is a big win, and they can get a system with exactly the same versions of everything with a simple 'bundle install' after a clean checkout!
Edit: 3. Also, there are likely to be C based python libraries you want to use that aren't maintained by your distro. Now you're in a situation where you are mixing multiple dependency management systems which gets ugly fast.
If you wish you can use JRuby and you don't need a C compiler.
Is Ruby really so slow that you can't do "Hello World" in Rails without leaping into a faster environment?
Java for OS X Lion: 62.53 MB; includes all basic tools to write Java code
Xcode for OS X Lion: 1.68 GB; is just a prereq for getting set up for cutting-edge Rails development
But Java and Xcode and Rails are really apples and oranges and pomegranates.
To get Rails running on a Mac, you simply have to install XCode, run "sudo gem install rails && rails new blog." The included system Ruby will work OK for Rails dev (it's what I use 99% of the time just for convenience). If installing XCode and editing things freaks you out, then you may not be cut out for the level of coding required to actually use Rails. Things like Try Ruby, Shoes, Scratch, etc. exist for a reason; trying to shoehorn people into Rails too early is a Bad Thing™.
If you don't have a Mac, you can get running on Windows using RailsInstaller. If you're on Linux, I think it's fair to assume you know enough to install Ruby and friends with your package manager.
TL;DR: It's not crazy to get started with Rails; it's probably far less painless than most frameworks these days. And pointing to a fairly poorly written, overly verbose getting started guide and saying "ZOMG STARTING WITH RAILS IS KARAZEEEE!" is just stupid.