StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I just started a Rails project a few weeks ago with Rails 3, and I've been quite happy so far.</p> <p>Some gems/plugins don't quite work yet. For example, Selenium and friends seem to be a little behind, though after trying a few plugins I finally got it working fine through <a href="https://github.com/jnicklas/capybara" rel="nofollow">Capybara</a>. <a href="https://github.com/rails/in_place_editing" rel="nofollow">In_place_editing</a> isn't working out-of-the-box for me (I suspect because of Rails 3), though there are alternatives and it's not complex at all. And I had some trouble with factory_girl, though apparently there is a <a href="https://github.com/thoughtbot/factory_girl_rails" rel="nofollow">version for Rails 3</a> now.</p> <p>But in general, most plugins I've tried seem to be working fine at this point. Maarons has already pointed you at <a href="http://www.railsplugins.org/plugins" rel="nofollow">RailsPlugins.org</a> if you want to check for a specific plugin.</p> <p>Finally, there are bunch of things that are just better in Rails 3 (see the <a href="http://edgeguides.rubyonrails.org/3_0_release_notes.html" rel="nofollow">release notes</a>). I used Rails 2 for a smaller project a while back, and using Rails 3 now, I was pleasantly surprised by the new routing (much less confusing), and the added bundler support (makes deploying much less scary).</p> <p>Since you're setting up a new project, I'll also mention that I've been quite happy with Ruby 1.9.2 (as opposed to 1.8.7). Check <a href="http://pragdave.blogs.pragprog.com/pragdave/2007/12/ruby-19right-fo.html" rel="nofollow">PragDave's blog post</a> for some major changes. The only thing that I recall needing explicit tinkering was the debugger -- just use the <code>ruby-debug19</code> gem and you'll be fine.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload