Upgrading any multi-threaded code to the latest stable ruby was highly likely to break everything. While they maintained the same API, completely changing the underlying threading module when your language supports C gems is not acceptable in any universe known to me. In ruby's case, 1.8's threads were greenthreads and 1.9's threads were kernel threads. The newest stable version often introduces breaking changes and it is often inadvisable to upgrade blindly without understanding what changes you're bringing into your codebase. Different upstream maintainers have a different concept of stable (my little pymumble fork and eglibc have very different notions of release quality).
Because being on the latest "stable" version of everything is rarely a good idea.
0 kommentar(er)
