News for hackers. Stuff that matters.
Re:Why Linux Succeeded by jmclnx on Saturday July 09, 2022 @12:43PM (#32036838)
> The GPLv2

Though this helped a lot, I believe the commandment "Do not change user space" was a much larger factor. In some upgrades of any of the BSDs, some user program will crash depending upon what changed in base. Linux, hardly ever happens, I have never had an issue with User Space on Linux Upgrades.

Re:Why Linux Succeeded by throw0101a on Sunday July 10, 2022 @10:25AM (#32045057)
> In some upgrades of any of the BSDs, some user program will crash depending upon what changed in base.

For FreeBSD at least, only in major version releases (12.x->13.x); with minor updates (13.1->13.2) there is API/ABI stability. (Free)BSD also has good kernel compatibility, so you don't have to worry about kernel drivers breaking 'randomly' with each update.

However, if you install the compatibility libraries then even recompiles may not be necessary:

* https://www.freshports.org/misc/compat12x/

* https://www.freshports.org/misc/compat11x/

* https://www.freshports.org/misc/compat10x/

* https://www.freshports.org/misc/compat[4…9]x/

Re:Why Linux Succeeded by onphonenow on Saturday July 09, 2022 @02:23PM (#32037900)
A good point. MS has done well with their compatibility efforts too. Wasn’t it don’t break vs don’t change?
Re:Why Linux Succeeded by kaba0 on Sunday July 10, 2022 @01:55AM (#32042214)
Isn’t linux kinda shitty in binary backwards compatibility? Sure, the kernel interface doesn’t break, but it doesn’t mean much in practice. Good luck running a binary that was compiled one Ubuntu LTS version before the current, let alone multiple years.

Windows does actually have superb backwards compatibility.

Re:Why Linux Succeeded by jmclnx on Tuesday July 12, 2022 @09:07AM (#32069300)
yes, you are correct, it is "Do not break user space", thanks.