32 ms·
It was forked in anger. A fair assumption is that there is at the very least some animosity on one side of the equation.
by mberning 15y ago
It was forked in anger. A fair assumption is that there is at the very least some animosity on one side of the equation.
- wfarr 15y agoIt was forked because while performance improvements are great to have, API breakage with no replacement for long-standing APIs is not. At the end of the day, people need a working environment and not everyone has the time of day to be updating every library out there that used a previously stable RubyGems API to use the new "better" ones (though I've yet to see a case where the API changes were little more than renaming a class and adding a couple class methods).
- nirvdrum 15y agoI know little about the API changes, but have been burned by just about every single release since 1.3.7. So much so that I now have to patch RVM every time I bring up a server so I can lock down the version. One could argue I should have been doing this right along, but I don't think it's entirely unreasonable to believe that new versions of your library loading software will continue to load your libraries.