3 ms·

How do you know?

bombcar 3y ago
Every single EOL product we’ve ever used has never been a priority issue until long after support has ended. It’s quite aggravating.
- worthless-trash 3y ago
  Its almost like companies fail to do software maintenance.
yoyohello13 3y ago
Personal experience, I think. People still complain about python 2.7 even though python 3 has been around for 15 years and python 2 was EOL 3 years ago.
- justizin 3y ago
  yeahp when there is load bearing python 2.7 code written by someone who has left, puts folks in a tough spot. :/
  - toyg 3y ago
    You're just more aware of technical debt you already had.
- hobobaggins 3y ago
  literally to have millions of lines in production code just in our company, untold billions or trillions of production Python2 code that works perfectly fine (well, did work) around the world. guess that will teach us to trust a scripting language for production systems!
  - znpy 3y ago
    Should have used perl5 i guess? /s
  - aforwardslash 3y ago
    So, whats the alternative? Try compiling a decade old java app and get ready for a surprise. Python2 was already dead 2 years ago. If your company did nothing to at least ensure the code runs, thats their problem. All languages go though deprecation and changes, except the dead ones - only if you had used *QBasic, you wouldnt have this problem. *the choice would be Cobol for most folks, but not only cobol isnt dead, it actually changes and deprecates stuff throughout the years - ex. Cobol77 vs cobol85.
  - somat 3y ago
    What's the problem? you have the source, nothing is stopping anybody from using python2. In fact from that perspective you could say it is a good thing, once python3 was published, the language python2 became more and more stable. Until we are at this point. The language is super stable. It will never change again. exactly what you wanted.
    - yjftsjthsd-h 3y ago
      > nothing is stopping anybody from using python2 Eh... pip+pypi killing support for python2 is kind of a big problem for continuing to use it unless you have zero external dependencies.
      - bombcar 3y ago
        This is the main difference between trying to get some ancient code written in C working vs "modern" toolchains - if you have the compiler and the code for C, everything is self-contained; many things like python2 download absolutely tons of support code and libraries to "build" - and when those go offline you can't easily build anymore; and you can't even say "this here VM will build this forever" unless you make sure that it will continue to work (and everything is separately cached/downloaded).

How do you know?

Every single EOL product we’ve ever used has never been a priority issue until long after support has ended. It’s quite aggravating.

worthless-trash 3y ago
Its almost like companies fail to do software maintenance.

yoyohello13 3y ago

Personal experience, I think. People still complain about python 2.7 even though python 3 has been around for 15 years and python 2 was EOL 3 years ago.

justizin 3y ago
yeahp when there is load bearing python 2.7 code written by someone who has left, puts folks in a tough spot. :/
- toyg 3y ago
  You're just more aware of technical debt you already had.
hobobaggins 3y ago
literally to have millions of lines in production code just in our company, untold billions or trillions of production Python2 code that works perfectly fine (well, did work) around the world. guess that will teach us to trust a scripting language for production systems!
- znpy 3y ago
  Should have used perl5 i guess? /s
- aforwardslash 3y ago
  So, whats the alternative? Try compiling a decade old java app and get ready for a surprise. Python2 was already dead 2 years ago. If your company did nothing to at least ensure the code runs, thats their problem. All languages go though deprecation and changes, except the dead ones - only if you had used *QBasic, you wouldnt have this problem. *the choice would be Cobol for most folks, but not only cobol isnt dead, it actually changes and deprecates stuff throughout the years - ex. Cobol77 vs cobol85.
- somat 3y ago
  What's the problem? you have the source, nothing is stopping anybody from using python2. In fact from that perspective you could say it is a good thing, once python3 was published, the language python2 became more and more stable. Until we are at this point. The language is super stable. It will never change again. exactly what you wanted.
  - yjftsjthsd-h 3y ago
    > nothing is stopping anybody from using python2 Eh... pip+pypi killing support for python2 is kind of a big problem for continuing to use it unless you have zero external dependencies.
    - bombcar 3y ago
      This is the main difference between trying to get some ancient code written in C working vs "modern" toolchains - if you have the compiler and the code for C, everything is self-contained; many things like python2 download absolutely tons of support code and libraries to "build" - and when those go offline you can't easily build anymore; and you can't even say "this here VM will build this forever" unless you make sure that it will continue to work (and everything is separately cached/downloaded).