6 ms·
Weird list of non-problems and not understanding how Linux works (and a few problems). A few points picked at random: There's no concept of drivers in Linux a
by rwmj 5y ago
Weird list of non-problems and not understanding how Linux works (and a few problems). A few points picked at random:
There's no concept of drivers in Linux aside from proprietary drivers for NVIDIA/AMD GPUs which are separate packages: almost all drivers are already either in the kernel or various complementary packages (like foomatic/sane/etc).
I would say this is a feature rather than a bug.
It's impossible for the user to understand whether their hardware is indeed supported by the running Linux distro and whether all the required drivers are indeed installed and working properly (e.g. all the firmware files are available and loaded or necessary printer filters are installed).
Your hardware generally either works or doesn't work. If you are looking for Linux-compatible hardware to purchase, you'll need to do a few internet searches first, which is the same as any other OS.
No high level, stable, sane (truly forward and backward compatible) and standardized API for developing GUI applications (like core Win32 API - most Windows 95 applications still run fine in Windows 10 - that's 24 years of binary compatibility). Both GTK and Qt (incompatible GTK versions 1, 2, 3, 4 and incompatible Qt versions 4, 5, 6 just for the last decade) don't strive to be backwards compatible. The Qt company also changed the licensing model for their toolkit which makes using the library under Linux problematic to say the least.
Complete misunderstanding of how Linux is distributed. The distros keep your software working with newer versions of Gtk or Qt, and deal with licensing. It's not something that end users need to worry about.
Also the obsession with "screen tearing"! I just don't get this frequent objection. I watch videos often in X11 which is supposed to be impossible because of this "tearing" thing, but somehow it doesn't bother me at all.
- nyanpasu64 5y ago> The distros keep your software working with newer versions of Gtk or Qt This doesn't help obscure software (like BambooTracker or vgmtrans) which isn't shipped by most distributions. Additionally a distribution isn't going to port a Qt 5 app to Qt 6 for you; if the original developer doesn't, someone else might do it a few years later, or never. Sure, a distribution might ship Qt 5 indefinitely, but it's going to slowly fall behind over the next few years, like what's been happening to Qt 4. Worse yet is software dependent on the KF5 KDE support libraries. Ironically, old creaky-looking software like Strawberry (based off Clementine, based off KDE 3's Amarok) and Qsynth/QjackCtl (dated look and feel) are the first ones to port to Qt 6 (before KDE applications), because they don't depend on KDE libraries which need to be ported first.
- kodah 5y agoThe desktop application ecosystem is kind of a mess from what I experienced; it's also possible I have the wrong expectations as I'm not usually building desktop apps. Gnome and QT generally have to be installed in order for apps that use them to work. I found that when I was trying to make an app, this ended up getting in my way far more than anticipated. There's a whole new class of electron-like (usually WebView oriented) frameworks appearing for languages now that make building desktop apps fairly straightforward. This is kinda nice because the framework then deals with environment integration (for instance X11 vs Wayland, or Windows and MacOS) -- but at a minimum it makes it so you can build native feeling apps that are entirely web frontends. The only limitation here is that I've found UI components for OS-native look and feel (as opposed to mobile) to be fairly limited in quantity. At the end of the day, I guess what I'm alluding to is maybe QT and Gnome are great, but I feel like a lot of applications that are outside of serving a particular OS or ecosystem will need to build with UIs meant to run on multiple machines with minimal dependencies.
- nyanpasu64 5y agoOn Windows, Electron-based apps generally bundle Electron (Chromium and Node.js) with the app, resulting in a large download size. You can do that with Windows Qt apps as well, and it generally works out too (the app is larger than a Win32 app but smaller than an Electron app). I have less experience with GTK but I assume it works the same. Linux distributions expect Qt and GTK apps to use a system toolkit. Some like Arch try to package Electron apps the same way (using a system Electron). However Electron releases incompatible major versions often, and you often have to install multiple Electron versions in parallel for different apps, and which version changes over time, so I have to juggle installing/uninstalling "electron" and "electron12/13/..." based on when apps update. (Admittedly, I also have Qt5/6 installed and GTK3/4 installed, but I expect these version numbers to remain stable for the next 5+ years.)
- PaulDavisThe1st 5y ago> There's a whole new class of electron-like (usually WebView oriented) frameworks appearing for languages now that make building desktop apps fairly straightforward. It was already fairly straightforward. Now it's just understandable to people who are mostly familiar with web-centric development, which is a different claim entirely. Qt is not an ecosystem; KDE is (like GNOME). Qt (like GTK, at least historically) cannot be an ecosystem because it has to be cross-platform. You can build GUI apps in Qt or in other GUI toolkits and they will just work. They do not need integration into a desktop environment (though it can help in some cases if they are. "OS-native look and feel" is overrated. There are numerous apps from Apple, particularly in the media creation sector, that do not conform to their own "native look and feel", and several of the most successful apps in this sector from 3rd parties also ignore it. Maybe for "office/productivity" apps it is important...
- pfortuny 5y agoHave you read the Security category?
- pfortuny 5y agoUntil you try to compile your Qt-4 software and… dang!
- Toutouxc 5y ago> I watch videos often in X11 which is supposed to be impossible because of this "tearing" thing, but somehow it doesn't bother me at all. It doesn't bother you or you don't have tearing?
- kevin_thibedeau 5y agoLike OP, I never have tearing in Xorg. I also will never own Nvidia. The issue isn't X11 which is perfectly happy to run in any environment including Wayland or GDI. It's crappy drivers that are handled by the B-team devs.
- kiwijamo 5y agoScreen tearing is something I've seen happen a few times across different hardware combinations. Sometimes it just works out of the box (e.g. my laptop using Intel graphics on Arch Linux experiences no tearing in any application) sometimes its a huge problem (e.g. my Raspberry Pi using ARM graphics experiences mild to severe screen tearing). Whats really confusing about the Raspberry Pi example is the conflicting info online. Some people swear turning off composting solves it, others say turning if on solves it. For me turning if off sorted it even tho this went against most of the advice I read in Raspberry Pi forums etc. Most of my experiences with Linux has been somewhere in between of the two extreme examples I've just described. Meanwhile Windows literally just works on every device I've tried it on. I can't remember the last time I saw any screen tearing of any kind on a non-Linux device. Whenever I'm out and about and see screen tearing I'm like "Ah it's running Linux" and chances are I'm right. For what's its worth I use Linux as the only OS on my ThinkPad and love it. I do acknowledge its flaws though and graphics is an area with room for improvement.
- spicybright 5y agoOnly time I've seen tearing in windows is when I had no graphics drivers installed. That really shouldn't be the baseline for an effective graphics driver...
- BiteCode_dev 5y agoThis is nitpicking and ignoring that the end users have problems because of all of this, and they are not addressed because of this kind of hand waving. I donate to the FSF, I contribute to FOSS, and I take those kind of articles very seriously. Because they contain very important informations of what we need to work on next. Of course, that doesn't mean we should take it at face values. Like for the Linux drivers situation, the idea is not to say "yeah, let's change that". But one should recognize the challenges it can bring, and find a way to make it better for those who wants to get hardware support. Staying on the top of our ivory tower while stating we are technically correct, the best kind of correct, is not a good long term strategy.
- psyc 5y ago> Weird list of non-problems and not understanding how Linux works I would like to add this attitude to the list.
- AnIdiotOnTheNet 5y agoYeah seriously. Been dealing with this attitude from the Linux Desktop community for literal decades now.
- spicybright 5y agoIt will never be the year of the linux desktop if they can't put their feet in the shoes of a non-linux hacker.
- sho_hn 5y ago> It will never be the year of the linux desktop if they can't put their feet in the shoes of a non-linux hacker. My honest impression is that the developers of the software are often quite in tune with the needs and pains of the users, and the sort of "your problem is not a problem" responses lacking empathy you see are largely from other users. This isn't universally true, but I would say broadly. And even in cases where it isn't that one uncaring dev is often not representative of the project as a whole. What I mean is - I think it's valid to call this a frequent failing of the broader Linux community, with users included. It bothers me as well. But the ones who do the most to make the software are often the ones who do care the most. And for them it's also quite a bad experience when generalizations go the other way.
- AnIdiotOnTheNet 5y ago> My honest impression is that the developers of the software are often quite in tune with the needs and pains of the users, and the sort of "your problem is not a problem" responses lacking empathy you see are largely from other users. Perhaps you have never perused the GNOME issue tracker then.
- 5y ago
- dylan-m 5y agoI think the GUI applications thing is another of those times where it's a tradeoff. Much like the way drivers work, it's fair to be annoyed with it, but it replaces (more or less equally) annoyances in Windows's opposite approach. Yes, your usual desktop Linux distro doesn't expect you to be running a GTK application that was built twenty years ago. If you do that, you probably need to do some manual steps. (That's why it installs to ~2 GB). On the other hand, GNOME uses one version of one UI toolkit across all of its core applications. If you click through the Settings application, you will not - at any point - come across a control panel from 1995. Meanwhile, want to make a native app for GNOME? Great, you have one option[1]. The lack of screwing around with backwards compatibility - freely dropping stuff when it isn't useful anymore - makes for a thinner, tidier stack in a lot of ways. It's better if we can have both - obviously it sucks knowing you'll have to "fix" something eventually because Lenart invented a newer better duotronic transporter buffer - and maybe stuff like flatpak will be able to help with that in the future, but I for one am grateful desktop Linux isn't forced to drag around a mountain of shims and forgotten libraries for a minority of users. [1] https://developer.gnome.org/ https://developer.gnome.org/
- eurasiantiger 5y agoThe author has monetised all outgoing links by showing an ad before redirecting. They are making money off this publicity, nothing more.
- poetaster 5y agoNo video tearing in years. Sure, I can haul an old laptop out of the basement. QT 5.6 is holding me back a bit. That is about money though and not linux. It is easier to absorb license fees in commercial software, sure. Need to read what the KDE people are doing.
- selfhoster11 5y agoScreen tearing is like keming - once you see it, you see it everywhere.
- bigpeopleareold 5y agoIt's least that one is possible to fix, at least with Intel graphics drivers. I get a little obsessed when I see deviations like this on the screen. That's one example, but there is also burnt pixels or pressure spots on the screen that can drive me nuts. Here's hoping for distros to make that solution the default.
- shadowgovt 5y ago> which is the same as any other OS Apple's value story is that you can get a machine guaranteed to run MacOS by walking into a store and buying their hardware, no Internet search necessary (unless you need directions to the store). There are a couple companies that do that for the Linux ecosystem, and I suspect it would make Linux easier to use if more were out there (but I don't know if the market would support them).
- giantrobot 5y ago> There are a couple companies that do that for the Linux ecosystem, and I suspect it would make Linux easier to use if more were out there (but I don't know if the market would support them). Even then those Linux systems are only supported with whatever distro the vendor ships. If you try to run a different distro that has license restrictions for closed binary blobs that "Linux machine" still may not work right.
- shadowgovt 5y agoYeah, and that might be as much a marketing problem as a technology problem. We may need to be considering another major category of desktop / laptop OS experience besides Windows, MacOSX, Chromebook, and "Linux (pick your distro)": "Linux (vendor)." Like Linux (pick your distro) but more likely to be working out-of-the-box and more likely to break under exotic manipulations than Linux (pick your distro). I have a great ThinkPad X1 that I just tried to switch the window manager it shipped with for xmonad. Everything broke. It's not particularly intuitive that the list of things depending on the window manager config involves wifi, audio control, Bluetooth control, power management (machine no longer sleeps when the screen is shut), screen auto-configuration when a monitor is plugged in or unplugged, and what happens when you plug a USB drive in... But they do. From an adoption standpoint, there might be meat on the bones of the messaging "Linux on the desktop is great if you buy from a vendor; just don't assume that any old hack you do to the default install is going to just work." Then widen the set of "blessed" hacks that do work from that base template of well-verified default configuration.
- Ginden 5y ago> which is the same as any other OS. Did you ever used Windows?
- heavyset_go 5y agoWayland fixed screen tearing. There's also the TearFree setting for Xorg.
- bitwize 5y agoI recently got a TI-99/4A and ran a program that did a pretty poor job of waiting for vblank to do sprite position updates. Result: Horrible, horrible tearing. You "don't have a problem with" tearing because tearing has always been with us and some people are just used to it. But other people are bothered by it and it doesn't have to be this way. Notably, one of the goals of Wayland is to solve for tearing when X hasn't.
- mschuster91 5y ago> you'll need to do a few internet searches first, which is the same as any other OS. For everything I can buy in a store I can be sure there's a Windows driver/userspace software, and for everything above a couple hundred dollars I can be reasonably sure there's an OS X solution (although that one seriously changed in the last years with the deprecation of 32-bit in 10.15 and the shitshow that is 11+). For Linux? Oh jesus. That requires dedicated research and, worst case, manually compiling stuff from some random github repository where someone hacked a solution.
- ahartmetz 5y agoAbout third-party drivers, especially from random Chinese vendors, I like to treat them like they don't exist. Mainline drivers tend to be higher quality, and they are more or less guaranteed to keep working indefinitely. The only exceptions I currently have are an nVidia GPU in a secondary computer (GPU compute box) and a Brother printer. Both have a long history of working well, and have packages, not tarballs or Git repositories that need compilation. The Brother drivers are also user space only. So, IMO, if you are doing it right, it's more a matter of research and less a matter of compiling your drivers from an obscure repository.
- rini17 5y agoSo, how to do it right? What are THE right steps to crosscheck stuff available from local vendor (to make eventual warranty claims easier) with linux compatibility? I am actually using linux desktop 20 years and still it feels like groping in the dark every time i buy some peripheral. Plus I can confirm the regressions mentioned in the article caused by relentless churn in the kernel are very real. Oh and userspace churn too. I have whole system from gcc4.9/Qt4 era saved to chroot into whenever I need some "old" software. For lay user such hoops are impossible.
- mschuster91 5y ago> I have whole system from gcc4.9/Qt4 era saved to chroot into whenever I need some "old" software. For lay user such hoops are impossible. A simple "docker run -it -v /:/mnt debian/eol:$CODENAME bash" should give you a working Debian chroot without any hassle - you can go as far back as Debian potato from 2000 per https://hub.docker.com/r/debian/eol/ https://hub.docker.com/r/debian/eol/. In theory according to a SO post (https://askubuntu.com/a/1161647 https://askubuntu.com/a/1161647) you should even be able to get GUI applications working inside a Docker container.
- jonathankoren 5y ago> Your hardware generally either works or doesn't work. If you are looking for Linux-compatible hardware to purchase, you'll need to do a few internet searches first, which is the same as any other OS. I'm sorry, but this simply isn't true. I've seen this specious argument for almost 30 years now. It was not true in 1994, and it is not true in 2021. The fact that this is still making the rounds, is perhaps the most damning indictment of desktop Linux. When making a hardware purchase for Windows or Mac, pretty much everything is supported right out of the box. I pick up a webcam, it works. I pick out a printer, it works. I don't have to worry the hardware is supported on Windows or Mac. It is, right out of the box. It's a very rare occurrence if I have to download anything to support it, and usually then it turns out to be needless OEM crapware. When it comes to Linux it's a crapshoot. Hardware description often don't say if it's supported. So you have start to google around and see if it's supported, and if you're lucky, you'll get get answer, but often you don't. Instead, you just find people asking if it is supported, or maybe talking about how it's kind of broken. A lot of this has to do with the fact that the kernel support is based on chipsets -- which makes sense from an engineering perspective -- but makes zero sense from a consumer perspective. This information isn't easily available. Purchasing desktop hardware for Linux is like walking in a minefield, and it's always been like that. You'll never get everything to work all at the same time, so you'll just have to satisfy yourself with which subset of features you want supported, but of course, you won't actually know what features are broken until you actually start using it, because you'll never list and test all your cases before purchase. While not stated in the above post, the lack of hardware support is often followed up with either a hopeful, "It's open source! It will get better!" Or a dismissive, "You've got the source. Fix it yourself." That's a lie. Even as a software engineer, I don't have the time or knowledge to develop my own driver for some sound card, or figure out why everything coming out of my printer has a pink a hue. I don't even know where to begin to debug that, and that's assuming I have the time to do it. If an SWE can't do it, there's zero hope for anyone else to fix their own problems. So what about the developer community? Surely they'll fix it! In my experience, the answer is probably not. I've never seen partially supported hardware go to full support. Either the developer moves on because it's "good enough" for him (e.g. see your comment about how screen tearing "doesn't bother me at all"), or some newer version comes out, and everything stops to (partially) support the new one. "Linux on the desktop" sounded great 20 years ago, and I really wanted it on my desktop. But then I realized that it's always tinkering. Desktop linux is like having a broken down car for your daily driver. What I wanted wasn't "Linux", but rather a unix for my desktop. Then MacOSX came out. An honest to god unix, but with hardware support. Once I made the jump, I haven't looked back. Now the only linux device I own are a raspberry pi and and an underused NAS. I'm cool with that.