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

If you 'incrementally' include changes which are incompatible, you end up with many more compatibility barriers to keep track of.

"Oh wait, this machine has foo 1.5.2, not 1.5.6!!!"

Though a solution to this scenario is to avoid including too many libraries in the standard distribution in the first place, so that incompatible changes in those libraries don't affect the base.

This in turn means that big packages with lots of dependencies would need to say "you need fooliba-1.5.6, foolibb-4.3.2, etc" instead of just "you need foo-5.2", but other languages do this and they seem to manage it alright.



Well, most other languages use the incremental approach, python is the outlier here.

I'm not saying one or the other is definitely better, just that I'm looking forward to the final judgement after this multi-year effort.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

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

Search: