3 ms·
> In fact, we're already running beta1 in production for Basecamp, so you know it's been taking a good beating. This helped us catch a couple of performance reg
by danso 13y ago
> In fact, we're already running beta1 in production for Basecamp, so you know it's been taking a good beating. This helped us catch a couple of performance regressions, and we've verified that everything is still spiffy fast on Basecamp.
Wow. Well, having enough faith to run Basecamp off of it -- and the fact that 4.0 was a very smooth transition from 3.2 -- is enough reason to play around with this beta for a project.
Edit: nevermind, don't think I can handle this feature removal:
https://github.com/rails/rails/commit/c300dca9963bda78b8f358dbcb59cabcdc5e1dc9 https://github.com/rails/rails/commit/c300dca9963bda78b8f358...
/s
- steveklabnik 13y agoI don't work at 37signals, but it's my understanding that Basecamp has often been running near HEAD Rails. Everyone on the team tries to keep some apps running on edge before a release to catch regressions.