Live data from Hacker News

Linux Problems on the Desktop (2018)

itvision.altervista.org

221–230 of 402 posts

Re: Linux Problems on the Desktop (2018)

#221
post #118

"Linux has a 255 bytes limitation for file names (this translates to just 63 four-byte characters in UTF-8) - not a great deal but copying or using files or directories with long names from your Windows PC can become a serious challenge." Not sure what he is speaking about.

I wondered about this as well, especially as Windows (10) still has issues with deeply nested (=long paths) structures. Especially in conjunction with OneDrive (forced upon me at work) it's an annoyance.

Re: Linux Problems on the Desktop (2018)

#222
I believe that those problems are the price of free development. When everybody can contribute anything, which is a good thing in itself, there is no streamlining or refining of the end product. There are soo many interfaces and standards which often are used in parallel that it's actually an achievement when a Linux system is still able to boot. Open Source is a good thing, but not in regards of user experience and stability. There is no guarantee for anything. When it works - it works. When it doesn't work - people will hopefully fix it, or at least contribute resources. When it doesn't work and nobody fixes it, what then? I wish I had the expertise so that I could fix everything myself if needed, but let's stay realistic. Nor have I resources to spare. I have to rely on others' efforts.

I've cross-compiled a Linux system from scratch for PowerPC once and it worked great. It worked up until I needed to recompile glibc because of some bugs threatening system security. Then everything went to hell. My prime interest in Linux and Open Source ceased to exist at this very moment. The dependency system in Linux is a nightmare, because basically there is none that guarantees consistency. How are cross- and circular dependencies even possible? And that's the price for freedom - chaos. It's great that anything works somehow. But there is no future to build upon.

Re: Linux Problems on the Desktop (2018)

#223

I've been running KDE Neon on NUC for a while, and Kubuntu before that since KDE 3.5 days. But still it's not ready to become my primary desktop. The main issue for me is RDP-like (not VNC-like) remote desktop experience. Without that I'm not even gonna try. I mean the kind where I check my desktop before I leave for work, resume the session remotely from work (when compiling or whatever), and pick up when I get home…

xfreerdp Just Works for me. Though I'll confess that I created the rdp file on a Windows machine, all I do is xfreerdp foo.rdp.

That's from Linux to Windows though, isn't it? I'm talking about from Windows/Linux to Linux.

Re: Linux Problems on the Desktop (2018)

#224

Earlier quoted context omitted.

>Unfortunately, Nvidia's so dominant (and rightly-so from a price-per-performance unit standpoint). I'm not sure about the price-per-performance. I just bought a new system with a Vega 64, and if you take into consideration I could use FreeSync instead of paying an extra $200 for GSync in a monitor, it works out better.

Pascal and newer Nvidia cards support Freesync as of driver version 417.71.

Oh yeah, they announced that a few weeks after my new PC arrived.

Re: Linux Problems on the Desktop (2018)

#225
post #120

Earlier quoted context omitted.

"This is a somewhat poor analogy, but it's sort of like a Chinese citizen (closed-source user) becoming a citizen of a democracy" I like that analogy (even though I am still looking for that pure democracy/open source government). In Linux you have the freedom to do allmost anything with the system, but you have to know what you are doing, as the system usually does not stop you, when you are about to do anything stu…

I like your expansion upon it :) I definitely do agree that "onboarding" could be improved. How I dunno. To me at least, it seems like I hear a lot of success stories from the tails of the spectrum - power users and developers on one side / the complete opposite on the other. And then for everybody in the middle, there's no other way to put it than it's almost a shit show: On the software side there a million and a h…

> stick with a non-high-DPI resolution screen

Sorry, this is impossible to do once you tried HiDPI. The difference is overwhelming; I consider non-HiDPI screens an obsolete technology like CRTs.

I do use Linux desktops; thankfully, the HiDPI support is much better these days than it was even 2 years ago. Both Gnome and KDE work relatively fine.

Re: Linux Problems on the Desktop (2018)

#226
post #181

Earlier quoted context omitted.

I'm using a dell XPS 13 (one of the new ones) and it works wonderfully. I don't run windows on it so I don't have any issues with my bootloader and I saw advice on the internet to get one with no nvidia gpu so I got one with intel graphics. It really does feel like a OSX level premium feel. The only bit I am missing is fractional dpi scaling which is apparently on the way but turning on big text in accessibility mode…

Can you plug it into a 4K display or all the shitty projector type things?

My XPS13 is plugged into a 4K display (thunderbolt -> displayport adapter) right now. Works fine.

Can’t promise projectors will work, but I would expect a thunderbolt -> HDMI adapter will work just as well as the Displayport one does.

Re: Linux Problems on the Desktop (2018)

#227

Earlier quoted context omitted.

It's an Nvidia problem. Nvidia's proprietary drivers suck and they're nasty to anybody who tries to develop open source drivers for their cards. AMD and Intel GPUs have been flawless plug-and-play for years now. AMD plays nice with linux developers and you should give them, not Nvidia, your money.

I was surprised when I saw the newest Vega firmwares show up in my /lib/firmware/amdgpu/ with a kernel update only 6 days after the release of the last AMD GPU -- and on Manjaro, where updates are supposedly delayed a little. AMD touted "day one Linux support", which I don't know if they fulfilled, but they're certainly more committed to Linux than Nvidia. Unfortunately, Nvidia's so dominant (and rightly-so from a pr…

> price-per-performance unit standpoint

On Windows sure (I assume), but that goes out the window when you use Linux. On Linux with an Nvidia card you're paying for more downtime/breakage, much worse performance with the FOSS drivers, incompatibility with wayland, etc.

Re: Linux Problems on the Desktop (2018)

#228

I wish that there would be one unified API for creating desktop programs on Linux. Right now it's somewhat coalesced on GTK/GNOME and Qt/KDE, though there are a number of others out there. I use Linux in a VM for very hobbyist level embedded development (think Arduino and the like). Driver problems are non-existent, all of the technical problems are non-issues in this environment. The problems that I see are all to d…

I'm sure that installing Atom and VS Code would introduce me to two more file pickers.

Having just checked, both Atom & VS Code use the GTK/Gnome file picker. LibreOffice is also using the GTK/Gnome file picker.

Re: Linux Problems on the Desktop (2018)

#230
Everyone for some reason expects that GNU/Linux should work on every hardware configuration. I don't understand that, honestly. Why is there no such requirement for MacOS? Why do Windows-certified hardware have to work flawlessly with GNU/Linux? Just buy a Desktop/Laptop certified for GNU/Linux and stop complaining.
Post reply on HN