Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> "planned obsolescence"

Cut me a break. In Go and Rust it's still easy to compile old code, and these languages have very strong backwards compatibility guarantees. You might need to compile it with a flag enabled, but it is going to compile and work.

Having the ability to improve on past language design mistakes over the years by deprecating old ways in favor of new ones is nice, and the burden of migration is generally minimal (or can be done automatically).



Go and Rust don't have old code. Talk in 30 years.


Sure, I agree that these guarantees still have to stand the test of time. So far they're holding up quite well.


If they stuck to binary libraries that would have been nice but since you have to build deps locally and match up the right versions, go and rust programs have been a constant headache for me similar to python. The version from debian repos never seems to be good enough, I have to install it from upstream and maintain it.


Not if you use any libraries. The whole venv/pyenv/pipx stuff of python needs to implemented for other languages too. Every program needing it's own virtual environment and tooling for every build.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: