Live data from Hacker News

Major Linux Problems on the Desktop, 2016 Edition

linuxfonts.narod.ru

331–340 of 384 posts

Re: Major Linux Problems on the Desktop, 2016 Edition

#331

I agree with all the points here. Despite all of this, Linux is still my preferred desktop. Why? The power! I can literally do anything with it. Including writing my own drivers/applications. Linux is my go to for doing things with zero crap. The same can't be said for Windows nor Mac. For me, this pro weighs very close to all of the cons I have experienced, experience daily, or will experience. Also as a desktop Lin…

“same can't be said for Windows” is subjective. I can do literally anything with my Windows. Including writing my own drivers/applications. And I can’t say the same about Linux. Not because that's impossible, but because I ain't a Linux developer.

Re: Major Linux Problems on the Desktop, 2016 Edition

#332

Linux users often take the idea of 'self-examination' way too far and it turns into 'self-disparagement'. The fact is, if you vet your hardware and use a major distro (Ubuntu, OpenSUSE, Fedora) you'll wind up with a perfectly functioning Linux desktop or laptop. You think about it, OSX only runs on a few laptops. Linux runs perfectly on more laptops than exist for OSX. Windows run on many laptops, more often than not…

Exactly. A non negligible part of his rant was about proprietary graphic drivers. Free software developers can't do anything about that, and anyway what is the point? Today, if you want to game just use Windows, if you want a fine Linux laptop get one with something like an Haswell with integrated graphics (or maybe Broadwell, still wait a little for Skylakes) And anyway if you look at what the "competition" sells wh…

I'm really waiting for the day an open source gpu with decent capabilities and clean design for simple drivers hit the market. The reverse engineering headaches are getting absurd these days.

Re: Major Linux Problems on the Desktop, 2016 Edition

#333
This is probably one of the theory vs. practice issues. While I admit that the article is mostly correct then again, in practice, I haven't had much trouble with Linux in the 00's and 10's while using Debian based distributions exclusively.

Surely I am not immune to the shortcomings of Linux but I don't remember having had to tweak my system as part of routine maintenance for... years. This was commonplace in the 90's. Merely upgrading or changing your X setup required tweaking configuration files, setting modelines and whatnot. I don't even know where the X configuration files live anymore. While the foundation is shallow, things generally work to the extent that I don't have to do "maintenance" on my Linux computers. Even external displays seem to work mostly just fine when presenting.

I haven't missed binary compatibility once: the distros compile everything anyway when libraries update. Compared to clinging to the cruft that makes 30 year old Windows programs work in Windows 10, I feel I'm better off with Linux even if I have to kill pulseaudio a couple of times each year and there's a slight chance that one of my laptops won't resume after suspend if it's unplugged.

I'm not saying that these Linux problems aren't problems. They exist and when they hit you, it hurts like hell. But my point is that Linux is imperfect as is the real world and people just tend to work around imperfections, again, like in the real world. So, mostly things work 5x better than 10 years ago and 50x better than 20 years ago.

Re: Major Linux Problems on the Desktop, 2016 Edition

#334
post #324

Interesting list. One of the biggest issues for me personally is the split effort. There are >300 distributions actively maintained, 300 projects whose sole purpose it is to package the kernel and some userland-stuff to make a usable operating system and provide for update mechanisms. 300 projects who spend resources on creating documentation, websites, giving support to users, ... And the simple truth is: It does no…

Same issue here: "Reported Web Forgery!"

It doesn't seem valid, I already took a quick look on my phone and did not see anything phishy.

Re: Major Linux Problems on the Desktop, 2016 Edition

#336
post #62

He's right. Many of the driver problems come from the fact that Linux finally worked on the desktop about the time desktop machines were replaced by laptops. Desktops with slots tended to have relatively well-defined hardware, and plugging in third party hardware was normal. This is much less true for laptops. OS development for laptops requires that laptop. It needs a Q/A organization which has one of everything you…

> The monolithic Linux kernel is just too big. What is it now, 20,000,000 lines? There's no hope of debugging that. It shows. That makes no sense. Most of that are drivers and platforms you won't ever use. And some forms of symbolic checkers exists for Linux (maybe not that advanced as for the Windows kernelspace, though, I don't know -- although even simple local heuristic checks are quite useful to check automatica…

Drivers and support for platforms should be separate from the kernel and work via a stable and well-designed API & ABI. The lack of this has been Linux's single biggest design flaw from the beginning.

Re: Major Linux Problems on the Desktop, 2016 Edition

#337

Earlier quoted context omitted.

Is the issue specific to terminal or are you seeing it somewhere else? The issue is that the default terminal behavior of ctrl+c sends a SIGINT to the running application[1], and so terminal programs override it with shift+ctrl+c, and likely add the shift for the others for consistency. I use "Terminator" as my terminal app - which allows you to set your keybindings - so I replace the "shift" in copy / paste and it's…

no please - I'm not talking about ctrl-C. I'm talking about CUA - https://en.wikipedia.org/wiki/IBM_Common_User_Access Even on OSX, the bindings that are used are cmd-c and cmd-v. It is universal - if you have never used the terminal, vim and firefox on a mac... I really urge you to do that. you'll see what i mean.

You've got the causality reversed. The Apple Lisa introduced the command-Z/X/C/V keyboard equivalents for undo/cut/copy/paste, and they were kept with the Macintosh and Apple IIgs.

IBM CUA and Microsoft Windows adopted them afterwards, adapted to the PC keyboard; I think Windows only adopted them with Windows 95 and NT4.

Re: Major Linux Problems on the Desktop, 2016 Edition

#338
post #222

Earlier quoted context omitted.

I... never said anything about these spaces, which I suspect you would agree require significantly different kernel design from a "desktop system" which is what this topic is supposedly about.

"Desktop system" is vague, but obviously u-kernels can serve as workstations, and hence desktops. CTOS was a major example of its day, if not the purest possible: https://en.wikipedia.org/wiki/Convergent_Technologies_Operat...

FWIW, CTOS was surprisingly unportable, which is hugely contradictory to the claimed advantages in this particular discussion.

Re: Major Linux Problems on the Desktop, 2016 Edition

#339

Earlier quoted context omitted.

> The monolithic Linux kernel is just too big. What is it now, 20,000,000 lines? There's no hope of debugging that. It shows. The Linux kernel is about 20MSLOC. The Windows kernel is about 50MSLOC. IIRC, OS X used to be ~80KSLOC. Problems with debugging are endemic to any monolithic kernel. Neither Windows nor OS X is easier to debug technologically , but Microsoft and Apple both have many employees and lots of money…

"...making their OS specific to their computers..." As a non-Linux open source project OS user, I am continually faced with driver deficiencies as a result of hardware specs being under NDA. A recurring idea I have which I am here sharing for the first time (apologies!) is: why not just pick a single item of hardware and build an open source, free OS project around it? Why? Hopefully, more control, to the extent poss…

Linux mostly works on most laptops. However, my next laptop is definitely going to at the very least be on Ubuntu's supported list and probably going to be either a Dell or system 76 with pre-installed Ubuntu.

Re: Major Linux Problems on the Desktop, 2016 Edition

#340
post #79

Earlier quoted context omitted.

Oh, this was an annoyance until I installed a clipboard manager (parcellite in my case) which automatically syncs the different clipboards.

But how do you paste? I mean I have all sort of keymaps to enable paste in vim using CUA (shift-insert), but try explaining that to a first time user. Its the small things that OSX does right.

Why would a "first time user" use a program that has a user interface designed in 1976? Why would a "first time user" expect this program to obey interface guidelines that did not exist until 11 years after that user interface was designed?
Post reply on HN