41–50 of 50 posts
Michael, great work as always. Your tutorials helped me to get up to speed on Rails quickly. Just curious, is there any particular reason you switched from GitHub to Bitbucket in your tutorial?
I have no affiliation with the author, but I'd recommend this book to pretty much anyone trying to learn Rails, I own the second edition. Before this book I'd never done any real web programming. My background is in compilers and trading systems/machine learning( those two are essentially one in the same), all C++ desktop software. The book got me up and running, better than any of the online rails tutorials, and the…
I actually recommend strongly against this book. It teaches things new people to Rails, let alone people new to programming, don't need to be messing with so early on. I'm mainly talking about the use of RSpec and some of the outdated Rails idioms. For myself and a few people I've mentored, Agile Web Development with Rails[0] has yielded much better results. If they follow that up with Eloquent Ruby[1] they will be g…
"100% default stack. The 3rd edition of the Ruby on Rails Tutorial uses the default Rails choices for all relevant technologies, thereby substantially reducing the configuration necessary to get started. The excellent but syntactically heavy RSpec testing framework has been replaced with the default Rails testing stack (MiniTest), making for a much gentler introduction to testing than in previous editions."
Earlier quoted context omitted.
I actually recommend strongly against this book. It teaches things new people to Rails, let alone people new to programming, don't need to be messing with so early on. I'm mainly talking about the use of RSpec and some of the outdated Rails idioms. For myself and a few people I've mentored, Agile Web Development with Rails[0] has yielded much better results. If they follow that up with Eloquent Ruby[1] they will be g…
yeah i wasn't too fond of the use of non-omakase stuff but i believe that is now resolved "100% default stack. The 3rd edition of the Ruby on Rails Tutorial uses the default Rails choices for all relevant technologies, thereby substantially reducing the configuration necessary to get started. The excellent but syntactically heavy RSpec testing framework has been replaced with the default Rails testing stack (MiniTest…
Similarly to what others have mentioned, I've also found Hartl's Ruby on Rails online edition to be the most comprehensive and impressive tutorial yet. I'd already had a strong foundation on Git, Heroku, TDD-testing, etc. but it was nice to see how they integrated so well with a Rails project and I personally believe they are both beneficial and critical for any web application development. However, after a cursory g…
[deleted]
This is also why criticisms of the sample app (e.g., a Twitter clone) are off the mark: all but the final two chapters are geared not toward a particular app, but rather to the general problem of web development. The last two chapters exist mainly to introduce some non-trivial data modeling, but once you have the foundation in place, you're ready to start building whatever kind of application you have in mind.
Earlier quoted context omitted.
Thanks for the suggestion and for the kind words. Instructions for setting up a local development environment are already effectively an appendix, because the Ruby on Rails Tutorial just defers to the excellent [InstallRails]( http://installrails.com/ ) service provided by One Month Rails.
Hello. Thank you so much for the book and the pioneering model that you have published it with. All the best on the platform for distribution. Please don't take the advice to downplay rspec. I think in chapter 8 you update the User model. It was so incredibly nice that, having been a week or so since I was able to work on the project, I was confident that the introduced changes did not break any functionality of the…
I think you may be confusing RSpec with testing generally. The 3rd edition replaces RSpec with the default Rails testing framework (MiniTest), but it still develops a thorough test suite.
Michael, great work as always. Your tutorials helped me to get up to speed on Rails quickly. Just curious, is there any particular reason you switched from GitHub to Bitbucket in your tutorial?
is there any particular reason you switched from GitHub to Bitbucket in your tutorial?
Yes, this is the subject of [Box 1.4](http://draft.railstutorial.org/book/beginning#aside-github_b...). The tl;dr is that Bitbucket is free for private repos, which for security purposes the new edition uses by default.
Michael, great work as always. Your tutorials helped me to get up to speed on Rails quickly. Just curious, is there any particular reason you switched from GitHub to Bitbucket in your tutorial?
I agree, great tutorials. I was also wondering the same thing about Bitbucket.
Earlier quoted context omitted.
I expect the full 3rd edition draft will be released within a couple of weeks. I hope to make a full launch (with screencasts) some time in October or November. I expect to use Rails 4.1 unless 4.2 is out of beta in time to use for the screencasts. I've compartmentalized the version-specific material, though, so I'm cautiously optimistic that I can swap in new Rails versions (even in the screencasts) as they're relea…
Do you intend to make use of new 4.2 goodness or simply make the tutorial 4.2-compatible? Granted, some of the improvements in 4.2 are out of scope for the book (like ActiveJob), some are performance related, but there is also web console. It fits the philosophy of the new edition perfectly and would be a useful addition to the book.
Earlier quoted context omitted.
I agree, great tutorials. I was also wondering the same thing about Bitbucket.
See [Box 1.4]( http://draft.railstutorial.org/book/beginning#aside-github_b... ). The tl;dr is that Bitbucket is free for private repos, which for security purposes the new edition uses by default.