Most apps worked out of the box. It feels like gimp is a little bit (very tiny) slower at starting. For OpenTTD i had to manually add the x11 access in flatseal. And for osu! it is the only way i can play the current version, and that just works.
Night light was the big one for me. If I remember correctly they wanted to implement a workaround for night light on nvidia gpus on wayland for KDE Plasma 6. I guess that’s kinda superfluous now 😄
Took me a second to figure out that was the Nvidia drivers version number. I was wondering if gnome made another major version shift from 45 to 545 for a second :)
All the problem I haven encountered with flatpak is short-term (GPU passthrough, wayland support etc), and all of them either dont work or require a one time fix.
Basically if I dont encounter problem on the frist day, I have never encounteted any problem after that, unless a update introduced some bug in the software, of course.
The couple of apps I use through flatpak has not had any issues as far as I can tell. Other than maybe being a little slow to get pushed to the newest version.
Image transcription. Pasted from source, Reddit Post
Despite having just 5.8% sales, over 38% of bug reports come from the Linux community
Article
38% of my bug reports come from the Linux community My game - ΔV: Rings of Saturn (shameless plug) - is out in Early Access for two years now, and as you can expect, there are bugs. But I did find that a disproportionally big amount of these bugs was reported by players using Linux to play. I started to investigate, and my findings did surprise me.
Let’s talk numbers. Percentages are easy to talk about, but when I read just them, I always wonder - what is the sample size? Is it small enough for the percentage to be just noise? As of today, I sold a little over 12,000 units of ΔV in total. 700 of these units were bought by Linux players. That’s 5.8%. I got 1040 bug reports in total, out of which roughly 400 are made by Linux players. That’s one report per 11.5 users on average, and one report per 1.75 Linux players. That’s right, an average Linux player will get you 650% more bug reports.
A lot of extra work for just 5.8% of extra units, right?
Wrong. Bugs exist whenever you know about them, or not. Do you know how many of these 400 bug reports were actually platform-specific? 3. Literally only 3 things were problems that came out just on Linux. The rest of them were affecting everyone - the thing is, the Linux community is exceptionally well trained in reporting bugs. That is just the open-source way. This 5.8% of players found 38% of all the bugs that affected everyone. Just like having your own 700-person strong QA team. That was not 38% extra work for me, that was just free QA!
But that’s not all. The report quality is stellar. I mean we have all seen bug reports like: “it crashes for me after a few hours”. Do you know what a developer can do with such a report? Feel sorry at best. You can’t really fix any bug unless you can replicate it, see it with your own eyes, peek inside and finally see that it’s fixed.
And with bug reports from Linux players is just something else. You get all the software/os versions, all the logs, you get core dumps and you get replication steps. Sometimes I got with the player over discord and we quickly iterated a few versions with progressive fixes to isolate the problem. You just don’t get that kind of engagement from anyone else.
Worth it? Oh, yes - at least for me. Not for the extra sales - although it’s nice. It’s worth it to get the massive feedback boost and free, hundred-people strong QA team on your side. An invaluable asset for an independent game studio.
Why does it create another user and put files under /home/linuxbrew/? Answer:
The script installs Homebrew to its default, supported, best prefix (/opt/homebrew for Apple Silicon, /usr/local for macOS Intel and /home/linuxbrew/.linuxbrew for Linux) so that you don’t need sudo after Homebrew’s initial installation when you brew install.
Where’s the logic in that? Why not just install to the user’s home directory so that you don’t even need root access in the first place?
Why is installing from the tarball unsupported and so frowned upon? FFS isn’t this just supposed to be a package manager? Why is everything so complicated and opinionated when compared to pip, cargo, Flatpak, etc? Compare this mess to Golang’s install and uninstall process where you literally just need to tar -xzf a file or rm -rf a directory.
Where’s the logic in that? Why not just install to the user’s home directory so that you don’t even need root access in the first place?
Excellent remark! Wow, that by itself already wrote it off for me.
Why is sudo hard-coded? Answer: it’s to prevent people from using doas and other sudo alternatives.
Another home-run! Especially as I’ve been a staunch user of doas for quite a while now and wouldn’t like to give up on that. Thank you so much for informing me on this!
Your third point is also interesting to ponder upon, though it wasn’t as impactful to me personally as the previous two were.
I would like to thank you once again for your astoundingly awesome insights on this matter! This comment has definitely contributed the most in me letting go of the thought of using Homebrew entirely (while some others already informed me that GUI-apps (mostly) can’t be installed from Homebrew to function on Linux anyways).
I’m not necessarily opposed to it, as I do use them if they’re inaccessible to me otherwise and if it’s official and up-to-date. But for security-sensitive apps (like a browser) I would rather not rely on it. Furthermore, it seems it’s unofficial anyways.
one of the most unappreciated aspects of any package manager is how they handle dependency resolution – the modern formats (Flatpak, Snap, AppImage) “solve” the problem by completely ignoring it altogether and just shoving everything-and-the-kitchen-sink into one blob – which works great as long as storage remains cheap or you’re not trying to develop for embedded systems
Same… The principal engineer on this project also referred to me learning C# as my first exposure to a “real programming language”
After already being advanced in Python
And familiar with C, C++, JavaScript.
I think what he meant by “real” is it comes out of the box with proprietary windows components that aren’t going to work anywhere else and don’t have human readable code.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.