Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Thought 1.9.3 is not very favorable for Rails deployment or am I wrong?


1.9.3 is stable and fine for deployment.


1.8.7 remains popular, but is declining, and for good reason. While there are some areas where 1.9 branches gave up ground (I'm looking at you `require` [1]), there are other areas where it absolutely smokes older versions; like date formatting functions [2]. Fortunately, Rails processes run for a long time under most app servers, so the performance regression of `require` isn't a huge deal. It is, however, very common to format dates as part of output, which may happen on hundres or thousands of records. There are also some nice features of 1.9 branches that are useful in a practical sense. For example, hash order is presered in Hash under 1.9, so you can get the extra features of a hash, and avoid superfulous sorting (can result in big compute savings).

[1] https://github.com/bradland/require-benchmarks

[2] https://gist.github.com/1352997


1.9.3 is great for production. You give up a bit of memory savings compared to REE (since Ruby proper won't be COW-friendly until 2.0), but 1.9.3 in general is faster, has a lot more features, and is widely supported by gems and libraries now.

1.8.7 has been EOL'd, which is as good a reason as any to upgrade.


Already in production for months, no particular problems


I just switched from 1.9.2 to 1.9.3 specifically because it cuts Rails startup time in half.


You are not even remotely close to being correct.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: