5 ms·
Uncommon? Yes. Very few people run Linux as a their primary OS.
by jki275 6y ago
Uncommon? Yes. Very few people run Linux as a their primary OS.
- ironmagma 6y agoNot sure why this is downvoted, it’s objective truth. I’ll go one farther though and say that Linux sucks, and in fact we must admit that if we want it to ever be good. It requires constant investment by the community to remain competitive with the other big players, who are constantly reshaping and making advances we need to keep up with. This is spoken as a desktop Linux user.
- bitcharmer 6y agoOut of curiosity; if Linux sucks, why do you still choose it over other systems?
- jki275 6y agoWhy would that surprise you, given the comment? The desire is to make it better, using it in spite of its issues is a way to do that. More users = more inertia to make it better, more resources for reporting issues, etc. I personally use Linux all the time, but not on the desktop because it's just bad enough that I can't stand it (It's really not Linux, it's X and all its associated crap). I won't criticize those who do because they want a better OS though, that's a good thing.
- bitcharmer 6y ago> Why would that surprise you, given the comment? Because people choose the least shitty solution for themselves whenever they can. So it doesn't make sense to torment yourself with an OS you don't like or cannot utilise to the extent that you'd like.
- ironmagma 6y agoIt's more about generativity. I have the capability to make this thing better, and I see vendor-imposed problems all the time with the proprietary solutions. Put two and two together and there's really only one responsible choice.
- ironmagma 6y agoOpen source software is great when it works, much better than proprietary software. I have a strong preference for open source; but I can't use Linux for anything serious because of how so many things are broken (not the kernel per se, so not "technically" Linux itself but the surrounding ecosystem). So, I use it as my hobby machine for whatever I can, because of dogfooding. The only way I will know what to fix, or even want to fix it, is by having to deal with it day after day.
- bitcharmer 6y agoBeen using Linux for work and as my daily driver for 10+ years. Never had any problem that would make me consider jumping ships. Professionally, I work with ultra-low latency systems for high frequency/algo trading and it would be impossible to achieve the level of tuning and performance that Linux offers on other OSes. I'm interested in the types of issues that made the experience bad for you.
- ironmagma 6y agoHere's a few... * Even though there is tons of extra swap space, running too many apps at once causes the entire system to become unresponsive for ~20s at a time. Granted, I am using older hardware, but there should be some minimal amount of responsiveness allocated to indicate the system isn't just totally dead. * Wifi GUI Gnome utility often ceases working and requires wifi to be turned off and on again. I got so fed up with this I just wrote a command to set Wifi to my credentials, and even then, I have to unplug/replug the wifi dongle frequently to get it to re-register with the system. On Arch Linux, this GUI utility doesn't even work at all. This has happened with multiple different makes of dongles. * When I was using Ubuntu for work purposes (and Python / node / Docker stack), it would frequently run out of file descriptors. There was no solution other than to restart. * Last night I started to encounter an issue where Ctrl-X would cut text successfully, but when I go to paste it, it will not be there. Possibly a bug with VSCode, not sure yet, but I haven't encountered it running VSCode on Mac at all. * Something about programs being interrupted by context switches to other programs that are using large slices of CPU time leads to input being misinterpreted. If I am running a Rust compilation in one window, typing `hello` into an adjacent terminal window might show up as `hellllllllllllllllllllllllllllllllllllllo`. This happens in a wide variety of applications. I suspect the problem has to do with input library routines not receiving real time priority, or something like that. Weirdly enough, I saw the same issue on FreeBSD.