3 ms·
Ruby 1.8 code does not just "stop working". Just as this 2020 Python2.7 political stunt won't stop anyone's code from working. The migration window was extende
by BuckRogers 11y ago
Ruby 1.8 code does not just "stop working". Just as this 2020 Python2.7 political stunt won't stop anyone's code from working.
The migration window was extended because the core development team didn't want to lose control of Python(2). Someone else would've taken control for sure, and for myself, I've already ported to PyPy4 instead of Python3.
A much easier transition than going to Python3 and nets you CPU performance and GIL-free Python.
- takeda 11y agoWhat I meant is that as time passes it's harder and harder to get working Ruby 1.8 installation. With RHEL for example you're guaranteed that there will be Python 2.7 until 2024, which delays adoption. As for PyPy4, majority of people don't chose python for performance. Even PyPy will perform worse than statically compiled languages. If performance is the goal, you should probably look into golang or even C.
- BuckRogers 11y agoYou can have the best of every world with Python on PyPy. Most people agree PyPy's performance levels reach the point of "good enough", while allowing you to write pure Python. Personally, I prefer to write Python over Go or C. No reason to not have your cake and eat it too.