Re:Reverting the incremental GC in Python 3.14 and 3.15
by lijok on Wednesday May 13, 2026 @01:55PM
(#48125208)
We should all go back to writing assembly
[ Parent
| on HN ]
Re:Reverting the incremental GC in Python 3.14 and 3.15
by __loam on Wednesday May 13, 2026 @03:04PM
(#48126028)
No we should write one of the many modern programming languages that handle certain projects way better, including kotlin, go, or Java. The only things python is best in class at are scripting and as a harness for high performance c++ or fortran.
Re:Reverting the incremental GC in Python 3.14 and 3.15
by lijok on Wednesday May 13, 2026 @04:45PM
(#48127311)
What about the projects that python handles better?
Re:Reverting the incremental GC in Python 3.14 and 3.15
by __loam on Thursday May 14, 2026 @04:07PM
(#48140542)
I mentioned those explicitly. People are still using it as a backend language for projects like huge SaaS deployments though, with the hypothesis being that dev time is expensive. With modern languages like kotlin and go, I think that gap is much too narrow to justify using a slow and badly designed language with good syntax.
Re:Reverting the incremental GC in Python 3.14 and 3.15
by 3836293648 on Wednesday May 13, 2026 @06:56PM
(#48128692)
> X is a terrible language because of the lack of static analysis available.
> (Mocking) Yes, that's why we should go back to Y with even worse static analysis.
Sure