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…
Major Linux Problems on the Desktop, 2016 Edition
71–80 of 384 posts
Re: Major Linux Problems on the Desktop, 2016 Edition
#72He'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…
Same thing with developing to put it on Apple laptops with that very specific hardware set, etc.
Re: Major Linux Problems on the Desktop, 2016 Edition
#73I have one more which this article doesn't mention: Bluetooth. It's an extremely fragile house of cards (as far as I can figure, there are a few kernel modules, dbus, a bluetooth daemon and pulseaudio involved) and every upgrade you roll is extremely risky. Currently my BT works but after a day or so uptime it will simply stop working and nothing short of reboot helps. (More https://bbs.archlinux.org/viewtopic.php?id…
Re: Major Linux Problems on the Desktop, 2016 Edition
#74I don't get articles like these. First of all this website is worse than any OS environment I've ever used. So right from that standpoint I sorta gulped a bit before reading on. Graphics driver issues in linux are nothing new, Nvidia a few years back started officially porting drivers to linux but that doesn't solve all the problems. There's also projects like Nouveau; so if you're complaining about linux desktop fro…
Re: Major Linux Problems on the Desktop, 2016 Edition
#75Earlier quoted context omitted.
> it's not uncommon to have to wait minutes for things to settle down after booting and logging in This is no longer my experience with Windows on an SSD. I'm always a bit shocked when I reboot and I'm back at my desktop in under 30 seconds. On a machine without an SSD, I'm annoyed at how slow everything is -- not just booting.
That's actually the reason windows is and will stay my main desktop system. Former Windows 7, now an "unfucked" Windows 10 Enterprise. It's just smoother than OSX or Linux Desktop and I always test some linux distros if I get new Hardware. Last time in novembre I upgrade to i7-6700k, Titan X, Samsung 950Pro 1TB. Of course it's necessary to have always at least one linux based server vm running I use putty to connect…
It has actually gotten to the point where it's stable enough for daily use now.
Re: Major Linux Problems on the Desktop, 2016 Edition
#76Earlier quoted context omitted.
> it's not uncommon to have to wait minutes for things to settle down after booting and logging in This is no longer my experience with Windows on an SSD. I'm always a bit shocked when I reboot and I'm back at my desktop in under 30 seconds. On a machine without an SSD, I'm annoyed at how slow everything is -- not just booting.
That's actually the reason windows is and will stay my main desktop system. Former Windows 7, now an "unfucked" Windows 10 Enterprise. It's just smoother than OSX or Linux Desktop and I always test some linux distros if I get new Hardware. Last time in novembre I upgrade to i7-6700k, Titan X, Samsung 950Pro 1TB. Of course it's necessary to have always at least one linux based server vm running I use putty to connect…
Re: Major Linux Problems on the Desktop, 2016 Edition
#77Earlier quoted context omitted.
Your single laptop datapoint sure makes this article invalid :)
The article is just as data free as my single data point. My experience contradicts it. I use Linux _everywhere_ these days, on the desktop, on the laptop, and on my workstation at work. It works well. It's just not Windows, which seems to be the author's main consternation.
It is not. The lack of a crash does not indicate lack of bugs. But, even a single crash confirms that bugs exist. (modulo the obvious)
Re: Major Linux Problems on the Desktop, 2016 Edition
#78I don't understand - I never see a mention of the biggest annoyance to developers on linux : consistent copy paste. It is a cognitive exercise to copy from the terminal or paste to the browser...or (the horror) copy from the terminal and paste on vim. It does not help that this works beautifully on the Mac. Is this not an annoyance to anyone else...and more importantly, considering all distros are now using libinput,…
Re: Major Linux Problems on the Desktop, 2016 Edition
#79I don't understand - I never see a mention of the biggest annoyance to developers on linux : consistent copy paste. It is a cognitive exercise to copy from the terminal or paste to the browser...or (the horror) copy from the terminal and paste on vim. It does not help that this works beautifully on the Mac. Is this not an annoyance to anyone else...and more importantly, considering all distros are now using libinput,…
Re: Major Linux Problems on the Desktop, 2016 Edition
#80Earlier quoted context omitted.
1.) "Everyone" is a very wide net to cast, considering people in THIS VERY comment thread try to prove how their personal GPU works so Linux is fine. 2.) It's a yearly review. The issues haven't gone away. That's why they're still listed, just because "everyone" knows them, they're still outstanding issues. You know, like GitHub issues - they don't go away UNTIL YOU FIX THAT.
facepalm 1)What are you even arguing? Yes some cards actually do work fine with linux I've had similar experiences 2) We have lists, and it's pretty funny they actually are Github issues! https://github.com/linuxmint/Cinnamon/issues for example As an actual linux developer, this webpage is fucking useless. It has no specifics on project or targets. Thats what a real development review is about. What do we have, what…
But that's combined with a lot of offputting content. E.g. the need to say everything is correct because Slashdot agrees and saying/suggesting Slashdot is unbiased and representative. Swearing at the developers who actually put in work (disagree heavily all you want, but no need to swear). Same for saying/suggesting that some developers don't mean well. Initially I only read the first part and thought it quite improved from the last time I read it. But no, again the argumentative stop energy. :-(
Further, a few of his issues are just opinions. Why combine that with the others?
Someone else said here: "he's right". Unfortunately not and again I already regret reading the various drivel parts.