3 ms·

There's a similar explanation for Linux's success on servers: Linus is very strict on backward compatibility for the kernel. But for Linux on desktop, the rest

by renox 6y ago

There's a similar explanation for Linux's success on servers: Linus is very strict on backward compatibility for the kernel. But for Linux on desktop, the rest of the stack (GUI environments) is made by a bunch of CADT devs who don't care about backward compatibility is, so of course it failed..

eecc 6y ago
CADT? What do you mean?
- gpderetta 6y ago
  google "CADT jwz". For various reasons it can't be linked from HN.
- brazzy 6y ago
  https://www.jwz.org/doc/cadt.html https://www.jwz.org/doc/cadt.html
- sobani 6y ago
  Cascade of Attention-Deficit Teenagers (open-source software development model)
pkaye 6y ago
What kind of backward compatibility for GUI environments are you talking about?
- AnIdiotOnTheNet 6y ago
  The kind where you can still use an application 2 years later without having to recompile it.
  - cycloptic 6y ago
    That generally isn't a problem if you pin/vendor your dependencies... the same thing that most developers seem to do on Windows and mac anyway.