The First Step for Ruby on Rails
jamesjohnson.me
The First Step for Ruby on Rails
1–10 of 40 posts
Re: The First Step for Ruby on Rails
#2After using rvm, I'd suggest using rbenv (https://github.com/sstephenson/rbenv) instead.
It doesn't try to do as much, so a little less magic. The biggest thing I like is that it doesn't try to do anything with gems, which is good - I've been trying to use bundler for everything.
Re: The First Step for Ruby on Rails
#3I've been following through the online version of Michael Hartl's RoR book: http://ruby.railstutorial.org/ruby-on-rails-tutorial-book
It's proven to be a GREAT way to learn the basics from the ground up while building an actual app at the same time.
Re: The First Step for Ruby on Rails
#4I've been following through the online version of Michael Hartl's RoR book: http://ruby.railstutorial.org/ruby-on-rails-tutorial-book It's proven to be a GREAT way to learn the basics from the ground up while building an actual app at the same time.
Fabulous introduction to Ruby on Rails, especially if you've already got some prior Ruby experience.
Re: The First Step for Ruby on Rails
#5After using rvm, I'd suggest using rbenv ( https://github.com/sstephenson/rbenv ) instead. It doesn't try to do as much, so a little less magic. The biggest thing I like is that it doesn't try to do anything with gems, which is good - I've been trying to use bundler for everything.
I hate to single you out, but it's become really hard for me to listen to any Ruby developers decry "magic" as a bad thing in RVM. RVM is an excellent tool that was taken down a notch by a hit job needlessly perpetrated by the author of rbenv.
RVM is no more magic than rbenv, and to listen to Ruby developers (who treasure "magic") talk about it as if RVM commits some cardial sin by overriding `cd` tops out my nerd-rage-meter. Ruby, home of the monkey patchers, has no place calling out RVM for overriding `cd`.
RVM and rbenv serve similar purposes. RVM gives you gemsets as well. You may not need them today, but they're there if you do. I use Ruby for a lot of system administrative tasks. These tasks run inside cron jobs and other places where a bundle really doesn't make sense. Despite the fact that they're no longer in vogue, gemsets are still very useful.
Should you check out rbenv? Yes. But the "little less magic" is a really poor basis by which you should evaluate it as a tool.
Re: The First Step for Ruby on Rails
#6After using rvm, I'd suggest using rbenv ( https://github.com/sstephenson/rbenv ) instead. It doesn't try to do as much, so a little less magic. The biggest thing I like is that it doesn't try to do anything with gems, which is good - I've been trying to use bundler for everything.
rvm still has more traction in the community and the end result is going to be very similar to rbenv for the majority of users--except that rvm has a built-in rubies installer + gemsets, which can make things easier for beginners to dive in and access other projects. New users should probably stick to rvm.
Re: The First Step for Ruby on Rails
#7After using rvm, I'd suggest using rbenv ( https://github.com/sstephenson/rbenv ) instead. It doesn't try to do as much, so a little less magic. The biggest thing I like is that it doesn't try to do anything with gems, which is good - I've been trying to use bundler for everything.
I hate to single you out, but it's become really hard for me to listen to any Ruby developers decry "magic" as a bad thing in RVM. RVM is an excellent tool that was taken down a notch by a hit job needlessly perpetrated by the author of rbenv. RVM is no more magic than rbenv, and to listen to Ruby developers (who treasure "magic") talk about it as if RVM commits some cardial sin by overriding `cd` tops out my nerd-ra…
As an RVM user, I wholeheartedly agree with your main point but I think there's an argument to be made to allow some other program handle gemsets. As it is, when you use RVM you most likely have to add your .rvmrc to your .gitignore. This unfortunately obfuscates what version of Ruby your project is on. Using rbenv is nice in that you can keep that documentation alongside the project where it belongs. Tying the gemset to the version is nice for testing various environments for a single project but doesn't work well when you have to choose between sharing a local development setting with the whole team or not sharing an rvmrc at all.
Re: The First Step for Ruby on Rails
#8After using rvm, I'd suggest using rbenv ( https://github.com/sstephenson/rbenv ) instead. It doesn't try to do as much, so a little less magic. The biggest thing I like is that it doesn't try to do anything with gems, which is good - I've been trying to use bundler for everything.
I hate to single you out, but it's become really hard for me to listen to any Ruby developers decry "magic" as a bad thing in RVM. RVM is an excellent tool that was taken down a notch by a hit job needlessly perpetrated by the author of rbenv. RVM is no more magic than rbenv, and to listen to Ruby developers (who treasure "magic") talk about it as if RVM commits some cardial sin by overriding `cd` tops out my nerd-ra…
rbenv is a bit easier to use in production (doesn't require any Capistrano addons, etc.) IMO, but for local dev it doesn't really matter one way or the other.
Re: The First Step for Ruby on Rails
#9After using rvm, I'd suggest using rbenv ( https://github.com/sstephenson/rbenv ) instead. It doesn't try to do as much, so a little less magic. The biggest thing I like is that it doesn't try to do anything with gems, which is good - I've been trying to use bundler for everything.
I have switched to rbenv myself, but that "magic" makes RVM a potentially better choice for a beginner.
* No need to install a second thing (ruby-build) to install rubies.
* No need to do manual things like running "rbenv rehash".
* More chatty and hand-holding (tells you dependencies you need to install for your platform, etc)
Re: The First Step for Ruby on Rails
#10After using rvm, I'd suggest using rbenv ( https://github.com/sstephenson/rbenv ) instead. It doesn't try to do as much, so a little less magic. The biggest thing I like is that it doesn't try to do anything with gems, which is good - I've been trying to use bundler for everything.
rvm still has more traction in the community and the end result is going to be very similar to rbenv for the majority of users--except that rvm has a built-in rubies installer + gemsets, which can make things easier for beginners to dive in and access other projects. New users should probably stick to rvm.
I tend to think that rvm is overkill for beginners. If you're really just getting started, installing ruby and rubygems is what you should stick to and adding steps like "install rvm" "install a ruby" "create a gemset" just add potential points of failure and frustration.
What is it about having gemsets that makes it easier for a beginner? Bundler seems to handle installing dependencies just fine.