5 ms·

This thread is depressing. It seems like so many of us are happy to build an incredibly fragile world.

• hannasanarion 6y ago
  This was announced 13 years ago. That's enough time to get an entire computer science doctorate and write your own alternative package manager from scratch, if you really need it so much. If Pip dropping py2 support today kills your app, it wasn't fragile, you were negligent.
  • blhack 6y ago
    Who are the people that are creating a fragile world here? The ones who didn’t rewrite their code to be compatible with the existing software called python, or the ones who didn’t rewrite their code to be compatible with the existing software that uses python? I don’t have any rights to python. If I chose not to rewrite my code for python3, I am increasing the fragility of the world. However the same is true for the python maintainers. If the maintainers were interested in maximum anti-fragility, Python3 should have been a fork. I’m not making any sort of moral judgement here. But I think it’s obvious both from the actions of devs not rewriting their software, and python being willing to make breaking changes, and that everybody seems to be blaming each other (and have been for a decade), that the goal here wasn’t really to create long lasting tools.
  • willis936 6y ago
    C code written 50 years ago is not EOL. Why is it acceptable that all code written in a specific language 15 years ago needs revisiting?
    • ForHackernews 6y ago
      Good luck getting 50 year old C code to compile on a modern system. I'm sure it's theoretically possible, but then, so is continuing to use Python 2.
    • hannasanarion 6y ago
      Python2 code still works. You just can't use a convenient package manager to grab libraries for it from a managed repository anymore. When has C ever had that?