Live data from Hacker News

Linux Problems on the Desktop (2018)

itvision.altervista.org

331–340 of 402 posts

Re: Linux Problems on the Desktop (2018)

#331

He's right, of course. The Linux community has been in denial about this for years. At the kernel level and close to it, the areas that consistently give trouble are video/GPU support and audio support. GPUs are hard, but there's no excuse for the mess in audio persisting for a decade. Video/GPU support is tough, but the current situation, where you have a choice of five different NVidia drivers for the same board, a…

> At the kernel level and close to it, the areas that consistently give trouble are video/GPU support and audio support.

... is this true? As a long time desktop Linux end user, whatever these lower level issues are, they've not been visible to me in at least a decade.

Re: Linux Problems on the Desktop (2018)

#334

I've been using a Google Pixelbook (their flagship Chromebook product) as my main development machine for the past couple months, and I love it. The ChromeOS "Crostini" project allows you to run a full Debian instance in a container, but with the other benefits of a Chromebook and ChromeOS. Each new release of ChromeOS brings better enhancements to Crostini, e.g. right now backups are manual but a native "one click"…

Oh cool. My 2017 MacBook Pro is just getting the stuck key issue. Is performance wise the chrome browser faster than the Windows one?

Apple will fix that for free btw.

I took my out of warranty 2017 mob and had no issues getting a repair.

Re: Linux Problems on the Desktop (2018)

#335

Earlier quoted context omitted.

> The only reason user accounts exist at all in Desktop OSs is that all of them today were originally server OSs. > "We managed to share home desktop computers in the 90s without significant problems, even though the OSs we used didn't support multiple user accounts at all." That's not true. Window 9x series had user accounts (with no security between them.) This was beneficial to users because computers were expensi…

Those aren't OS-level accounts, they have no (local) permissions system applied to them, they're just profiles. Regardless, I can assure you that basically nobody used them in the 90s.

I can assure you, they got a lot of use in the 90s, and they were used for exactly the same reason people still make separate accounts for their family members on their computers today. It's not about security. It's about keeping separate preferences.

Your hypothesis that XP somehow forced the concept of separate accounts on regular home users because NT was used on servers is just bizarre. People who wanted separate accounts were doing it on 98, and people who didn't simply ignored it and all shared one account. The UX for different family members sharing a single computer by signing into it existed before the NT kernel was in use around the home. The implementation changed when Windows went to NT, but the UX did not. And given that the UX of separate accounts was already appreciated by users, the more robust implementation made possible by NT was a no brainer.

>Mobile OSs got this right: on a personal device,

When it comes to a PC, "personal" is a misnomer. Failure to understand that is the root of your confusion. You are presumably at a place in life where your computer is your computer, not shared with others, like your cell phone. But when it comes to PCs, that perspective is a privileged one. It's evidently not important to you that numerous people be able to use your computer, but it is important to others. The UX of the device that lives in your pocket needs to be different from the UX of a device that sits in the middle of your living room for the whole family to use, like a television.

Re: Linux Problems on the Desktop (2018)

#336

Earlier quoted context omitted.

I have found its super dependent on what hardware you get, Especially on laptops. I always pick hardware that works perfectly with linux and I am left with a very premium experience but when using linux on bad hardware like macbooks and broadcom wifi everything just doesn't work right.

I have a MacBook that is malfunctioning under MacOS (it's running at 60-80% CPU usage when idle, known problem, no fix available). I tried installing Linux on it, couldn't get it working at all. I have a Dell XPS15, specifically chosen because the XPS line is supposed to work well with Linux. Numerous problems, all related to drivers. But the main problem is that every time Windows updates it wipes out GRUB. I figure…

The XPS 15 doesn't have a linux "developer edition", but it still plays quite well with Linux (even if it's less "plug and play" than the 13 model). It comes with Nvidia Optimus and that is still not supported on Linux (thanks to Nvidia) so you may want to either turn off the dGPU or use bumblebee. The HDMI port is wired to the Intel GPU so it should just work. In the future, just to be sure, I advise you to check the Archwiki: the most popular laptops have a page there, reporting all the working and non working stuff and eventually some work-arounds

Re: Linux Problems on the Desktop (2018)

#337

Earlier quoted context omitted.

All that has been doable for quite some time, you could mount SMB shares like that with smbfs since early releases of Samba, and later with the CIFS fs driver. You do need root to mount things that way, so it isn't ideal. For the more complicated stuff it can be done but not everything is available via a simple GUI. GNOME and KDE have their own virtual filesystem layers in userspace, GVfs and KIO, I don't know what K…

These aren't the same thing though. The GNOME and KDE VFS layers only apply for applications written for those APIs. It's not a universal thing. Being able to mount a CIFS filesystem is fine, but it's not the same thing. In Windows, you can basically use a UNC path anywhere because CreateFile knows how to deal with it. The point is that you don't need to mount the remote filesystem (the Windows-equivalent being mappi…

There is currently no kernel interface that I know of to do that, and I don't think it would be too hard to hook into an open() on an invalid path and try to do something (mount a network fs, call out to GVfs or KIO, etc), but I can tell you you will meet resistance if you try to because things like "//stuff" and "smb://stuff" are already valid local file paths in Linux. So I leave it up to you to figure out how to do this without breaking things.

Re: Linux Problems on the Desktop (2018)

#338
post #304

Earlier quoted context omitted.

>Stop buying NVidia hardware. They actively sabotage Linux development. AMD is much better in that regard. Buy AMD instead. Sadly if you work with Deep Learning buying AMD is a surefire way to make most of the work published by others unusable without serious effort.

Is the number crunching side as terrible as the visualization side?

OpenCL is very limited versus CUDA in terms of language support, tooling and libraries.

Re: Linux Problems on the Desktop (2018)

#339
post #247

Earlier quoted context omitted.

I've been using Linux since about the same time, and while I find the five-broken-implementations thing rather exhausting at times, I am more than thankful for it. It's one of the reasons why Linux (and FOSS software) is so damn useful. Just look at Windows land, where they do have one implementation to rule them all, more or less (Windows 10). Everyone who dislikes its telemetry or almost touch-only interface is eit…

I really want to know how GNOME 3 even saw the light of day, and why distros like Fedora even went with it. Unusable.

Easy, Red-Hat used to pay the salaries for a big chunk of GTK/GNOME developers.

Re: Linux Problems on the Desktop (2018)

#340
post #311

Earlier quoted context omitted.

> Linux is literally the most used operating system on phone... So what happens if/when Google switches to Fuchsia on their phones?

They can't. I mean they can on their phones. But that's a tiny percentage of the total Android HW. All the big SoC vendors would have to get on board and rewrite their milions of lines of their kernel code on top of Fuchsia. Android is also not just phones, but also on tablets, tv boxes, etc. This would just cause even more fragmentation in the Android ecosystem.

Google Play Services access contract.
Post reply on HN