|
|
|
|
|
by jimmaswell
19 days ago
|
|
> There's no equivalent of python2->python3 schism and the package management churn I tried to run a Ruby script recently and got an error about Fixnum. Apparently they made some breaking change to how integer types are referenced in version 3. I had to modify the script to get it to work on a modern parser. How is this not equivalent to the Python 2-3 jump? I don't know the first thing about Ruby but this already told me that it's a language with breaking changes between versions. (It was the ruby scripts here if anyone is curious: https://github.com/haberman/vtparse/ ) |
|
The same way triping on a small pothole is not the same as falling into a giant sinkhole.
The claim was not that Ruby had no incompatible changes whatsoever.