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

I also like old carburetors and simple electronics, but we're in the vast, vast minority. Most people want a car they don't have to think about or understand, looks pretty, and will take it to a shop when something goes wrong.
 help



It’s also possible for a system to both be a “carburetor type” while also being well-considered and elegant in design and function so it’s easy to tinker on if you want to, but doesn’t need that 99% of the time. I just don’t think that’s ever been a serious goal of any desktop-oriented Linux distro or DE. They all embrace the complexity and add to or multiply it.

From my ~25 years of using Gentoo Linux, I'd say that it's exactly what you describe in your first sentence. The complexity is there if you want it, but only if you want it.

Gentoo is quite a bit more work to get set up than other distros, but

* Once you get it set up, it just keeps on going

* If you're already fairly familiar with Linux system administration, the setup process isn't hard... it just involves a lot of waiting, unless you use the distro-provided precompiled packages

* There's really good documentation that walks you through the installation process and leaves you with a computer with a functioning bootloader and kernel, Internet access, and some pointers towards what you might want to install next


I agree about system design, but I think - especially in the context of your networking example - the complexity lives below the OS and not a case where it's a lack of effort.

Networking protocols, connections, error states, etc are inherently complex and require equally sophisticated handling that linux may not always do. Some software chooses not to handle at all and expose directly to the user - but others like KDE simply lack the millions of dev-hours of polish that Windows and Mac have.


Agree that this is an area that this is an area where complexity is unavoidable.

As for KDE polish, the only reason that’s true is because of someone’s choice to not put energy toward that part of the desktop.


Is it that simple though? There could be so many other reasons. Maybe the particular issue is related to a specific hardware or network configuration that the developers have never run into or can't reproduce.

Linux needs polish for sure, but given a finite amount of time, energy, and money the reasons are likely more complicated than "they don't care"


What's a "carburetor"?

A touchstone for people who forget that engines have been fuel injected for decades.

My great-grandfather - a carpenter in the 1930s - apparently had a saying: "If a man can make it, a man can fix it."

While /technically/ still true, I lament that it is increasingly inapplicable to the world around us today.




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

Search: