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

His reasoning makes sense but, as all developers tend to do, he spots an error in a system and wants to switch to another or invent a new one. You know the xkcd.

Often times the solution is just to work together and fix the old one. For me the logical fix would be to patch all kinds of malicious, undefined or non-spec behaviors in LTS releases in short cycles regardless whether the developer thinks, it is security-critical or not. To make this more feasible you could either pay for it or use a minimal base system separated from the user-space. Both exists today.



That's both a lot of work and a lot of churn, though - people choose LTS because they don't want things to change!


In a sense, things do not change, they stop to be changed from a assumed state.




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

Search: