Now that’s what I call a quality meme.

The installer is a little bit less polished for now (until Leap 16.0 with the Agama installer drops as stable release), but generally… I guess? It just doesn’t come with Canonical’s shitty ideas.

The problems of (Open)SUSE is in its backend. A lot of tech debt from the days SUSE S.A. was owned by Novell, they screwed up a lot. But their OBS system is solid (explanation: for distro-users it’s basically like the AUR), and they don’t do silly nonsense with Snaps but stick with Flatpak. Or you know, alias’ing apt install commands to snap install like Ubuntu does…

It’s a really solid choice for a daily driver. Just the Nvidia driver sometimes causes issues, but what else is new.

Fair enough, that indeed sounds like a regression (assuming your old device got officially supported hardware) and a lack of GUI settings. I 100% concur this sucks, both.

I’m still very critical when someone complains that “Linux” doesn’t work properly on a laptop. Most of the time it’s not the fault of any FOSS project, but device manufacturers doing wonky shit that requires device-specific workarounds or license nonsense making support hard to impossible. Especially power management is an issue with newer laptops (which of course doesn’t apply to you) sometimes not even properly supporting e.g. S3 standby because they expect very weird Windows-behaviour (not even standard S0 but some wonky other stuff). I see way, WAY too many “Windows vs. Linux” comparisons on Windows machines that then conclude Linux “not being ready yet” (sometimes even blaming the devs). Meanwhile FOSS developers are being utterly exploited.

Sorry for lashing out a little bit.

Pretending that Linux doesn’t have issues is an outright lie at this point

And I’m sure your comparison is done using a Linux-native device, not an originally Windows-specific device you installed Linux on? With power management specifically there’s nothing Linux distros can do to work nicely everywhere, it’s an awful clusterfuck.

The only way to fairly attribute flaws to Linux is to compare a device that waa designed and built for both. Otherwise I could blame, idk, Android for running like shit on my Wii U.

<rant> The funniest thing about it is the reason why they won’t create an extension API: developer freedom. Because some extensions would stop working with an API, according to them. (Which is a damn weak reason, nothing prevents them from keeping the unstable patch path open and let users decide if they want to install potentially dangerous extensions or just those marked as “safe”, i.e. API-only).

Despite being told they actively decided against such an API I of course was still hit with the “just build it yourself and make a PR” line. Yeah, sure, who doesn’t want to waste dozens to hundred of hours for an already rejected concept?

That’s the same people who brought us libadwaita, which is in fact so well known for developer freedom that Linux Mint saw it as a necessity to fork it into libadapta to reintroduce more freedom. </rant>

God I’m so annoyed by this. Gnome’s organisational structure screws the whole desktop. At least that’s something they’re partially aware of…

And because Gnome still lets every extension monkey-patch code right into the shell your whole desktop may crashes in the middle of your work. Especially if the extension devs aren’t monitoring changes in Gnome 24/7.

Happened to me 3 times before I moved to KDE. Which I very much dislike in comparison, but it’s just way more stable. Couldn’t go without extensions in Gnome either because of the very smooth-brained decision to replace the tray icons with their own backend, so any app not supporting their way of doing it either disappears into the void or has their tray icon submenu inaccessible.

Ugh. I love the UI/UX of Gnome, but in terms of stability and compatibility they screwed up phenomenally.

Their corpo stuff is (incl. Latitudes). Their consumer stuff (like XPS) apparently not so much.

lol

I’ve always assumed [GTK] was specific to linux and used to make apps that look a certain way (like they were made for gnome) vs allowing you to make UIs the way you want to.

That definition more or less applies to Libadwaita, which is basically a fork of GTK4 but specifically for Gnome with lack of proper theming. However both of those Frameworks can be used on any desktop platform. It’s just not very common to be used outside of Linux.

There’s also Libadapta, a fork of Libadwaita that reintroduces theming capabilities. Both it and GTK4 can be themed with CSS, so you can very much make it look however you want. One example of something that’s GTK but absolutely doesn’t look like it would be KlipperScreen.

That explains so, so much. Not just why everything wants to connect somewhere, but also disasters like programs with >1000 npm package dependencies. Why learning the right way if you’ve always been told to go the easy way.

Unfortunately nothing that can be done about it unless someome creates an “illegal” kernel module which supports HDMI 2.1 despite the lack of license. That’s basically the only hope right now (and I’m all for it).

Because it sucks? 🙃

Like, seriously, Manjaro had so many problems already that were completely preventable, makes stupid mistakes, bloats itself up with nonsense and provides no stability improvement over Arch whatsoever (which is a bad thing). On the contrary, it apparently even introduces additional bugs.

I’m not surprised they accidentally DDoS’ed the AUR, given they also have a docker script that spins up every single time an image is downloaded to push a change to git to increment a counter. Every. Single. Time. A full docker container. From scratch.

I’d only ever recommend Manjaro to people I really don’t like.

trying to do desktop apps with decent looking UIs that work across Linux/Windows/Mac is a nightmare

I’d argue that both Qt as well as GTK is right there for the taking… but those are not “industry-standard”.

Fortunately this kind of thinking slowly but surely gets defeated, although we still have to fight for every inch of user-friendliness (and even modern security concepts) against elitists.

Unfortunately right now most documentation is still crap for average users, and people who keep repeating bullshit like “it’s better to provide CLI commands because they’re universal” (actual nonsense people keep saying) don’t make it better. The situation is so phenomenally bad that I’d outright assume Mistral AI with “Reflection” on to be more useful to newcomers when looking for solutions (on case a friendly professional or enthusiast isn’t available), because that thing is less likely to provide an outdated command for the wrong distro than a google search. Which is an absolutely abysmal place to be in for Linux as a whole if we want to keep the rising adoption train going.

This. Terminology, unknown concepts (some simply expected to be known, such as standard parameter syntax) and a lack of simple examples to understand all the abstract explanations with (like the way ‘tealdeer’ presents it) make manpages utterly useless to anyone but powerusers with lots of time and an interest in the topic.

Someone saying “RTFM” unironically in regards to Linux is basically a red flag for new users at this point. Not because reading manuals was bad, but because the manuals provided are simply awful. They’re developer- and expert-friendly, not user-friendly.

Or, in case of Linux, you just suffer because the manpages are so god damn useless to average users.

And FTFM. Find the fucking manual.

And perhaps TTFM. Translate the fucking manual either from broken chinese-english or the tech-lingo + missing context information which is almost every manpage on Linux, making it nearly useless for the average user unless you got hours and hours of time to understand all the adjacent concepts and commands.

Not sure about the availability in your region, however I have good experiences with AVM Fritz!Box routers. They are proprietary but extremely easy and reliable without sacrifycing security or features. They’re from a german company and basically the go-to router vendor here by both ISPs and in retail.

This, so much this. Although it’s equally old grumpy farts as well as script kiddies. You’ll be able to identify the former by their trademark quote “Systemd is the end of / nail in the coffin for Linux”.

In a few decades we’ll have Linux rainbow press delivering the newest (partially made-up) drama of Linux celebs and influencers to the senior Linux users sitting in their electric FOSS rocking chairs, talking about the good ol’ days with X11, SysVinit and no god damn sandboxing or immutability.

And they’ll feel ALIVE thanks to it.