Hacker News

points by skeledrew 2 days ago | 0 comments

And PHP is quite the hot mess. Always has been, really. See the security issues over the years, including the most recent for example. Meanwhile I've never seen any serious issues for Python that's triggered mass required fixing. There's something to be said for moving carefully and ensuring things aren't broken to the best of one's ability, which is the SC's purpose.

[–] pjmlp 2 days ago

https://app.opencve.io/cve/?product=python&vendor=python

[–] skeledrew 2 days ago

Are you helping me to prove my point? I see 156 results, with 1 in 2023 and the rest before that. Meanwhile there are 801 results with at least a dozen in 2026 for PHP[0], and we still have 2 more months to go.

[0] https://app.opencve.io/cve/?vendor=php

[–] pjmlp 2 days ago

Hardly, one CVE is enough.

[–] skeledrew 2 days ago

Not at all. I specifically stated "serious issues for Python that's triggered mass required fixing", ie. it was so bad that there were public notices for users to update ASAP. The closest thing I can find is CVE-2022-34265, and that's in Django, not Python itself.

[–] pjmlp 2 days ago

Python is hardly used at PHP scale for Web development.

[–] skeledrew 1 day ago

Agreed. And Python usage is far more diversified. But I fail to see the relevance of usage to a language being stable vs ridden with issues. Well, beyond that one would expect the one being so many things to so many different communities would have more issues than the other used by a single community for a single purpose.