5 ms·
That's an unfair comparison. You are building the whole Ruby dev environment from scratch before coming to Rails. Which is not what is happening in the tutorial
by pkd 10y ago
That's an unfair comparison. You are building the whole Ruby dev environment from scratch before coming to Rails. Which is not what is happening in the tutorial. Actually, if you have the typical ruby environment setup already (ruby, rubygems, bundler), then its only
gem install rails
rails new
rails s
You don't need postgres or any JS runtime to start off.
- bdcravens 10y agoIf you were trying to learn Rails (which this story ostensibly is doing with React) you wouldn't have Ruby installed. (or you'd be using system Ruby, which you generally shouldn't use: https://robots.thoughtbot.com/psa-do-not-use-system-ruby https://robots.thoughtbot.com/psa-do-not-use-system-ruby)
- pkd 10y ago> If you were trying to learn Rails (which this story ostensibly is doing with React) you wouldn't have Ruby installed Why? I went to Rails after I learnt Ruby. By that time, I already had rvm installed to manage Rubies. I can agree that a lot of users jump to Rails without learning Ruby first, in which case the setup will be 4 commands longer. But that is not the case with React as you can't jump over JavaScript to React directly.
- Klathmon 10y agoAnd you don't need 80% of the stuff in the article to start off either, this is a VERY in depth walkthrough...