3 ms·

Java is younger than Python.

by xapata 5y ago

p_l 5y ago
But Java 1.0 code is still (mostly) compile-able on recent Java versions, not so much with Python where I'd worry about going back 5 years.
- musicale 5y ago
  Many Python developers and users were burned when the Python project decided to set fire to billions of lines of code. I have zero trust in Python as far as code longevity is concerned.
  - throwawayapples 5y ago
    More like trillions of lines of code, from probably millions of developers, dating back to the 90's. "The total code size of Zope 2 and its dependencies has decreased by over 200,000 lines of code as a result." - from the 2013 Zope documentation... how many lines of code was it before then? Python really burned its bridges. It's shown that it's a toy language now, and demonstrably unfit for any real production-quality projects.
    - xapata 5y ago
      Right right right. I'll let my CTO know.
    - EdwardDiego 5y ago
      > how many lines of code was [Zope] before then? Soooo many. Zope was a very formidable code base to delve into. I was trying to learn it because my company was using Plone, and Zope quickly surfaced through the abstractions. Zope's codebase might have been more accessible if type annotations were a thing back then. Their implementation of "interfaces" for Python were very interesting back in the Python 2.3 days. I disagree that Python is a "toy" language now. It started out as one, and has been stumbling awkwardly away from that ever since the mid 2000s - virtualenvs, pip, pyenv, pipenv/poetry, type annotations, mypy etc. In my entirely unscientific opinion, I think it was Django that started this journey, then of course scikit, numpy leading into pandas etc.
      - xapata 5y ago
        Both NumPy and Django were created in 2005, but Numeric, the ancestor of NumPy, is nearly as old as Python itself, and predates SciPy.
    - darthrupert 5y ago
      Bullshit. 2 => 3 transition was mostly mechanical and programmers who are unable to do it should get better. I haven't seen py2 code in several years. Granted, I would look away in disgust if I did.
- xapata 5y ago
  I wrote code that worked with both interpreters simultaneously for many years. I don't know why you'd worry so much.

Java is younger than Python.

by xapata 5y ago

Java is younger than Python.

p_l 5y ago

But Java 1.0 code is still (mostly) compile-able on recent Java versions, not so much with Python where I'd worry about going back 5 years.

musicale 5y ago
Many Python developers and users were burned when the Python project decided to set fire to billions of lines of code. I have zero trust in Python as far as code longevity is concerned.
- throwawayapples 5y ago
  More like trillions of lines of code, from probably millions of developers, dating back to the 90's. "The total code size of Zope 2 and its dependencies has decreased by over 200,000 lines of code as a result." - from the 2013 Zope documentation... how many lines of code was it before then? Python really burned its bridges. It's shown that it's a toy language now, and demonstrably unfit for any real production-quality projects.
  - xapata 5y ago
    Right right right. I'll let my CTO know.
  - EdwardDiego 5y ago
    > how many lines of code was [Zope] before then? Soooo many. Zope was a very formidable code base to delve into. I was trying to learn it because my company was using Plone, and Zope quickly surfaced through the abstractions. Zope's codebase might have been more accessible if type annotations were a thing back then. Their implementation of "interfaces" for Python were very interesting back in the Python 2.3 days. I disagree that Python is a "toy" language now. It started out as one, and has been stumbling awkwardly away from that ever since the mid 2000s - virtualenvs, pip, pyenv, pipenv/poetry, type annotations, mypy etc. In my entirely unscientific opinion, I think it was Django that started this journey, then of course scikit, numpy leading into pandas etc.
    - xapata 5y ago
      Both NumPy and Django were created in 2005, but Numeric, the ancestor of NumPy, is nearly as old as Python itself, and predates SciPy.
  - darthrupert 5y ago
    Bullshit. 2 => 3 transition was mostly mechanical and programmers who are unable to do it should get better. I haven't seen py2 code in several years. Granted, I would look away in disgust if I did.
xapata 5y ago
I wrote code that worked with both interpreters simultaneously for many years. I don't know why you'd worry so much.