As a die-hard linux user, this line of thinking really plays against Linux. Software distribution hasn't caused problems in windows since XP. Likewise, all mac users seem pretty happy with .app bundles.
> Second, linux distribution maintainers are usually much better informed about the technical details of installing software in a stable manner than any software vendor. Sure you can get your software from the vendor. But then you should be willing to accept that it is often broken, inefficient, and insecure. Software vendors have no interest whatsoever in installing their software in a professional and sustainable way on your system, package maintainers do.
Do you realise how insulting this comes across ? As a software dev, my personal experience of "professional linux distro packagers" is people literally removing random lines of code of my software until it builds - who cares if it crashes as soon as you do more than open it anyways. I'd rather not have my software packaged than have it like that. My subjective experience from the software I use is that stuff like AppImage made straight by the dev is generally much more stable and works much better than whatever chtonian hack a debian packager decided to apply.
That is, at least in my experience, very false. They often do care about build systems more than the maintainers, as they're the ones who have to make it work for everyone.
I've worked with the Gentoo packagers and those people I have interacted with have a lot of knowledge about how to distribute software. It's not for nothing the Gentoo community has to push changes upstream when upstream assumptions don't hold up downstream.
Every interaction I've had with packagers has been them trying to make the build system work for their single distro. None of them have ever tried to help make it work for "everyone" running linux, much less spend any time thinking about the other two platforms that have 90% of the actual users.
IME they also tend to be much more focused on making the build system work on their distro than making the actual software work. Not surprising given that that's what they know, but they tend to be perfectly happy to make changes which cause functional problems to get things to build.
> As a software dev, my personal experience of "professional linux distro packagers" is people literally removing random lines of code of my software until it builds
I'm sorry this happened, but I can assure you that the vast majority of maintainers do not do anything like this.
Mac user here, can't ever remember encountering post-install errors with Mac software in 15+ years (bugs sure, like every software has, but nothing related to incomplete installation or whatever)...
>Linux packages have a higher bar to meet for integration quality
Isn't it actually a lower bar?
They don't have to follow the platform's look and feel and UI libs (there isn't a standard, a distro can package Gnome, GTK+ only, KDE, XFCE, even CDE and Athena stuff, plus all kinds of ad-hoc UIs). They don't have to work with the same shortcuts, use the same system for configuration, or even play well with the same window compositor...
When it comes to "integration quality" in Linux it's mostly "compiles with the distro's version of libs".
Sorry to say, but I have to raise my hand here.
The only post-installation issues I ever had on Mac and Windows were related to drivers, not applications.
Plus since like a decade or so, I rarely "install" software on Windows anyway, because all the tools I use come as a "portable" version, which is just a ZIP archive.
In an Apple-like fashion, these "just work" after unpacking to an arbitrary location (e.g. a USB-stick or SD-card)...
What am I doing wrong here? ¯\_(ツ)_/¯
It's most of the time difficult, and sometimes impossible, which is very user hostile; I, the user, should be deciding which version of the software I want to run, not the distribution.
Because the newer version (of the lib, I presume) changes the ABI and borks all the packages that were compiled against the old version?
Trying to upgrade something like Mesa from Rawhide or whatever is just going to mess up your install like nobody's business but if you just need a couple minor libs (for a specific program) I've not had any problems.
For programs, I've had ones running for years after they got dropped from the distros with zero problems or that I built and installed from some random srpm I found on the interwebs.
In all honesty the only 'song & dance' I have to do on a semi-regular basis is rebuild my python modules when Python gets updated on a distro upgrade.
But with any distro, you call install whatever you like wherever you want. You, the user, make that call. You, the user, should have the knowledge to tidy up if it goes wrong.
Installing anything outside of distro repositories and Flatpak (& alternatives) is, in most cases, PITA.
Tracking down missing dependencies, figuring out which libraries are compatible, downloading source for those libraries, because the system provided are outdated, etc. You can literally spend a whole day just building a somewhat simple application.
I'm not a fan of binary blobs, like it's customary on macOS/Windows, but at least I can actually use an application in a minute or so, after downloading it. There is no fussing around, it just simply works.
Because they have huge teams maintaining API and ABI stability.
On any Linux distribution worth its name you can also use the software within seconds after installation. The teams are just smaller and their approach is more centralised and principled, but I never had a problem using, e.g., emacs after installing it.
You need to fuss around with software from their parties. Simply because these third parties do not care enough about your Linux to make the installation work well. These same third parties also do not care much about how stuff is supposed to work under windows, they just drop their binaries and assume that the windows ABI will somehow keep working.
Maybe that observation is incorrect, please give me data points. Also this won't mean you have to run Debian (but maybe a VM with Debian in it).
I don't remember the last time that happened. Not that I'd exchange my ArchLinux setup against either but you gotta be honest - installing stuff on windows and mac is a solved problem.
However the number of times a Debian or Ubuntu update borked something... that I don't have enough fingers nor toes - I had at least 3 installs of debian that I fucked up enough that I couldn't recover them in the last ten years - in comparison the last time that happened for me on windows was in 98' era. Not that windows doesn't suck - I still get the occasional BSOD even on win10 while Linux kernel panics are... uncommon for me but that's just my experience).
For most user-facing Mac software that comes with a GUI, there are no post-install. Installation simply consists of copying the application bundle into the /Applications folder.
That's sad. But fortunately, not all packagers are like this. As a software dev too, I have a great experience with packagers from various distributions. When they have an issue (either build or runtime) they tell me about it and we discuss a patch together that I include in my next release.
> My subjective experience from the software I use is that stuff like AppImage made straight by the dev is generally much more stable and works much better than whatever chtonian hack a debian packager decided to apply.
Sure it works if you are in the most common case (Linux on x86_64), but it has some downsides:
* It only supports CPU architectures the dev can build for
* It only supports operating systems the dev can build for
* The dev needs to publish an update every time there is a vulnerability in a bundled dependency (assuming they are even watching for vulnerabilities)
If you don't know what you are missing, you won't miss it.
Nothing, unless you have a application-specific upgrade daemon running. Sounds like a good design, right? :)
The automatic update process breaks software by making incompatible changes, thus preventing a security problem by just not allowing me to run the software in the first place?
The windows way of installing software (download random .exe or .msi files from random websites on the internet) has been a problem for every non tech-savy people and the people helping them manage their computer forever.
Every modern OS comes with its own package manager nowadays for a good reason.
I still maintain that for all its many technical and architectural faults, the biggest thing holding back wider Linux Desktop adoption is the Linux Desktop community itself.
You most likely do know your software better, after all, you wrote it. However, their concern is the integration of your software into larger system, and they may well be more familiar with those issues than you are.
In all my years of (Debian) distribution maintenance, this was the most typical cause of disagreement between packagers and upstreams. It's very common for upstreams to make fairly arbitrary decisions which might make sense in the context of an individual project, but which are not appropriate when considered as part of the system as an integrated whole. Neither are wrong per se, but as an upstream, your focus is on your project and it's easy to miss the bigger picture issues. Conversely, packagers' focus upon the system as a whole, so their view is at a higher level.
Additional to this, don't just discount the knowledge and expertise of distribution maintainers. There are of course some who just blindly package up other people's work and aren't experts. However, there are others who are software authors in their own right, with decades of accumulated experience and understanding. The latter may well know more than you do, and might be able to provide some keen insights you could benefit from. There are an awful lot of developers who don't know how to make software releases properly in a way that allows it to be consumed straightforwardly by others, with proper understanding of API and ABI issues, proper versioning, and proper use of build systems.
Rabbit's nest but the commonly accepted community API for font discovery is fontconfig.
> How do you know if the system is on battery?
Again, rabbit's nest but the commonly accepted community API for this used to be DeviceKit-Power. Then pm-utils. Now I think you're supposed to use UPower or poke through /sys/class/power_supply?
https://upower.freedesktop.org/docs/Device.html
I wrote the battery applet five years ago in gnome-shell and even I can't keep up.
> How do you make sure that the temporary directory your service needs is actually mounted and writable?
In theory /run and systemd-tempfiles are new enough standards but that hasn't stopped a misguided packager from misinterpreting a policy and patching my software to support /tmp, which was not a tmpfs on their distribution, causing users to blame me and send bugs my way.
For all the things it gets wrong, Docker removes an entire class of misconfiguration errors that allows for more reproducibility and automation in configuring systems, and they do this partly by making the distribution irrelevant.
For Linux to be a world-class OS, it needs to step up its ABI and distribution game and figure out how to squash bickering over things like application menu standards.
Isn't this an admission that linux is worse? Less skilled developers can successfully create working applications for Windows/Mac because they have unified and documented APIs to access these operations. But on linux you have a heterogeneous system that uses standards developed 50 years ago and require greater expertise to work with.
"My system is harder to use" is not a selling point.
Unless you're a Linux Desktop evangelist, then it is because it lets you feel smugly superior to people who don't like wasting their time with shit like this.
And the one thing I absolutely loved about Linux is that it does what I say. On Windows 10 there are things that are impossible to get rid of. That new browser that automatically adds itself to the desktop icons? Or the Onedrive icon in the explorer which you can only remove through registry hacks (and which might come back at any time after a update).
Customising Windows is so amazingly hard and cumbersome, I was just blown away how easy and straightforward this was on Linux.
I once gave my mother a Ubuntu installation after I had been particularilly annoyed by a malware she managed to catch on her Windows 7 machine. She has no idea how to use computers, but she really loved Ubuntu and told me it feels much clearer. She used it for nearly 4 years till the hardware died. To my surprise she had significantly less questions about how to do $x than before.
My feeling is that the Linux desktop can be great for people with very simple needs or very advanced needs. It is that middle ground where it currently sucks I guess.
It kind of is when the reason it is is a corollary to fundamentally supporting letting you and your User community do whatever they want. I've used Slackware, Debian, Ubuntu and MacOS; and to be frank, at least with Linux, even if I do have some greater degree of exposure to dependency/ABI hell, I'm free to determine my own approach to meeting those challenges.
With Windows/MacOS,you have a 500 pound gorilla shoving sh*t down your throat because they decided it's better for them. I simply cobble together a workable solution for the use-cases my Users really need, keep it simple, well-defined and documented, and most importantly, kick software or decisions that impact my freedom as a sysadmin to run the system I'm fine and dandy to maintain to the curb.
To hell with devs who don't respect rule number 1 of system architecture: the System one is helpless to influence or get to understand is the first thing to go when the chips are on the table. At least for me anyway.
No one is trying to sell you a system. If you want your software to work well on Red Hat, Debian, and BSD then you either play with their respective standards or you let the maintainers do their job. Just stop whining that these systems are not windows and you need someone to that work for free but exactly the way you want it done.
If you feel well inside Apples walled garden, have fun there, but don't come complaining when some Unix tool or programming language does not work there.
And no, Red Hat or Debian is not harder to use than MacOS. It just supports way more nontrivial use cases out of the box. That comes with a certain complexity. If you don't need that, no one suggests you run it on your desktop.
I disagree. People have been recommending Linux to people with non-complex needs for a long time, especially since Ubuntu went mainstream. “No one suggests you run it on your desktop” is thus wrong.
> If you feel well inside Apples walled garden, have fun there, but don't come complaining when some Unix tool or programming language does not work there.
Is this really an issue? As far as I’ve heard, macOS is a POSIX-compatible system with a BSD userland, and most Unix tools work fine. Checking out the Homebrew repos, it seems like all the Unix tools I’m used to are there. And even some Linux-specific systems like FUSE have been ported to macOS. As far as I can tell, macOS thus supports Unix tools and programming languages as well as most Linux distros.
As I see it, it'd take someone with a lot of political connections and political capital in the Linux ecosystem to be able to pull it off successfully. I have neither.
Second, linux distribution maintainers are usually much better informed about the technical details of installing software in a stable manner than any software vendor. Sure you can get your software from the vendor. But then you should be willing to accept that it is often broken, inefficient, and insecure. Software vendors have no interest whatsoever in installing their software in a professional and sustainable way on your system, package maintainers do.