Unix style command line where "everything" is text...
I thought that was a good idea? Why isn't it so? What should be the alternative?
Ask HN: What did Linux not do right?
61–70 of 173 posts
Re: Ask HN: What did Linux not do right?
#62Earlier quoted context omitted.
1 working proprietary driver is better than 5 half-assed open source drivers
You see my thought is that a lot of proprietary drivers end up being half assed, and kernal code tends to be pretty good. Your mileage may vary though.
Re: Ask HN: What did Linux not do right?
#63Earlier quoted context omitted.
I thought that was a good idea? Why isn't it so? What should be the alternative?
Having some structure like power shell would be really nice.
Re: Ask HN: What did Linux not do right?
#64Disk I/O. It's basically all blocking except the fairly recent io_uring which is much more than disk I/O and perhaps a bit daunting for "I want to write some data without starving my main thread." I wish you could use select() and poll() on regular files on disk, like you can for almost all other file descriptors.
Re: Ask HN: What did Linux not do right?
#65Re: Ask HN: What did Linux not do right?
#66Re: Ask HN: What did Linux not do right?
#67How Linux freezes under high memory usage, Mac OS and Windows both handle such situations well without requiring a hard reboot.
Re: Ask HN: What did Linux not do right?
#68Not Linux, but Systemd[0] makes many people angry. Entire distros have purposefully not included it. Look at Devuan[1] [0] https://en.m.wikipedia.org/wiki/Systemd [1] https://www.devuan.org/
Re: Ask HN: What did Linux not do right?
#69The desktop experience is still a mess. They’ve become complacent with ‘it works out of the box’ but that’s not the bar. Apple sets the bar and there’s no prize for second place. You’re on Apple or Linux or brain damaged and using Windows, but nobodies using two as their primary driver, and so one ecosystem dominates. I’m glad it’s Apple because the GNU crowd are virtue signalers first and software developers second.…
Re: Ask HN: What did Linux not do right?
#70This fragmentation has real downsides, too. I have an odd multimonitor setup with one vertical monitor and two horizontal monitors. I can configure this in KDE's settings, but the login shell is a separate application and needs to be fixed by googling the solution and changing some config file. I've never had a Linux distro that, when I configure the default monitor when logged in, also uses that setting when logged out. In all my years of using Windows this has never happened!
In some ways, this is one of the ways in which a company controlled project has more of a chance to succeed than a community-built open source project. They have a financial incentive to stick to one plan and do it well, rather than develop a dozen competing products and brute-force a good solution. The user-facing areas of Linux that do the best are projects like Android, Ubuntu, and Pop OS, all of which have a company that keeps them in line.
This is to say nothing of the google-centric UI of Linux. Don't know how do do something? Google the answer, sifting through multiple possibly out-of-date forum posts, or excavate through man pages to find the answer. In other operating systems, you can confidently rely on the OS helping you out, but not Linux. This behavior is often dismissed as "hand-holding". Well, I suppose I want my hand to be held then! I don't want to waste time finding the answer online, I want the OS to show me to the answer so that I can find it for myself. I can never remember the correct syntax for systemctl commands; I don't use them often enough to memorize them. So I have to look them up every time. Windows, meanwhile, has provided a GUI (that I know will exist on every Windows machine) that I can use to stop and start these things. In fact, Windows has provided a tool that I can easily use to troubleshoot the system, without having to google for commands first, that is easily accessible. Meanwhile the Linux answer is "here, learn how these dozens of commands and how these dozens of config files work; if you encounter enough problems you'll start to memorize stuff." The stench of Stockholm Syndrome is strong.
People complain about the difference between Program Files and Program Files (x86) in Windows. Well let me introduce you to the dozen different places to install an executable in Linux! Also, half of them are sim-linked to the other half in an effort to decrease confusion (they seem to have failed there).
Yes there are problems with Windows. The registry should have been an actual database, dark mode isn't os-wide, and most of the settings still haven't been corralled away from winforms into the new settings app (though you can't seriously be suggesting that Linux's "put a config file anywhere in whatever file format you like" system is better). I want to like Linux but every time I try it I end up having frustrating problems that take way longer to solve than they would on Windows.
Edit: Holy moly, sorry for the accidental essay. Hadn't realized how long this had become