Just for a bit of context, this guy is mainly famous in the Linux community for his “Linux Sucks” series he used to do annually, with a light-hearted but pinpoint approach to tackling the main problems with the Linux desktop in general. That is, until the pandemic hit. Then he just unleashed his inner fascist that was probably always there.
Then his content became mostly complaining about “woke culture” mainly in Mozilla and the GNOME team, “cancel culture” after the whole schtick with RMS and his behaviour and probably his worst take yet to this day, reducing Linus Torvalds himself to a “vaccine passport company employee” when he yelled GTFO to another guy spreading misinformation about vaccines in the Linux kernel mailing list.
tl;dr the guy got famous for good content and then became publicly the complete ass he probably always was
Oh, it’s firefox-gnome-theme mixed with firefox-vertical-tabs. I usually use the dark mode variant, but switched to the light one for the screenshot for a better contrast.
I do wonder how much the aesthetic will change.
I can really talk about the aesthetic changes due to using the shell-theme-upstream “theme”, which now gives the option to have or not the rounded corners. It looks weird at first, specially after years of being used to having one, but we’ll get used to it. It’s not a make-or-break thing for the desktop.
To be honest it just looks a bit more like macOS now.
I also wonder what those corners will look like when a window is maximized
It always filled the corners whenever a window was maximized, but the rounded corners of the top bar were drawn over everything the desktop shows, like a GIMP layer that sits on top of every other one. Now that it is gone it just shows a the regular corners of the window, like this:
Not necessarily that Linux need a single distribution, but having more standartized tools for the job. Like Flatpak for package management or Pipewire for audio stack, or finally being able to use Wayland as a daily driver, stuff like that.
Like, not having to search around to find out what kind of package your specific distro uses for that particular thing just to begin to search around to troubleshoot your problem.
Issues are issues, even if they don’t look like issues on your end.
- I hate anticheat as much as the next person, but it needs to work, since companies refuse to stop using those, and the average “competitive FPS gamer” won’t care if the company decided to not update the anti-cheat version to support Linux, all they’ll see is that the game they want to play doesn’t work (which happened and got into Luke’s relationship with his friends);
- Also having a couple specific games that are difficult/impossible to run is also a fucking pain in the ass (and I say that as someone who has dealt with this a lot before). You spend hours looking for a way to make the game run when on Windows all you’d need to do is hit “play”;
You should try having basic empathy for other people.
One of the things that libadwaita brings to the table that could have never been done without it in GNOME is accent color customization (that isn’t going to make it into 42, but maybe in 43 or 44), just like elementaryOS does with Pantheon; and the app itself can be recolored in many ways with some of the new features (like it already does with Metadata Cleaner).
It’s not a lot of customization in the hands of the users, but it brings loads of possibilites for the app developers themselves and guarantees that their apps won’t look broken due to some poorly implemented theme like it used to do with GTK3.
Flatkill
Dear god, people are still using it as a source? See the Response to Flatkill.org as well, if you want every single point.
I am not in favour of these flatpacks/snaps or whatever these things are called
If you don’t even know what they’re called (and snaps and flatpaks are definitely not the same thing, look into it) then why be so opinionated about it? learn why they exist and how they work.
Packages should be distro packages, always.
Easier said than done, that would only leave space for huge projects maintained by either a huge community or by a large corporation, with smaller projects struggling to maintain every single application out there, SPECIALLY if you want linux as a whole to grow and have more widely available software.
Arch Linux is the perfect example of how failed this mindset is, where the main selling point of the distribution is how widely available every single software you need is there, but most of those are found not in the official repositories, but in an unnoficial, user-maintained and verified repository that unfortunately has the potential to be abused (either to spread broken packages or even malware, but fortunately, has been really well maintained for all these years).
And the vendor of the software should never be responsible of packaging, thats literally the job of the distribution.
That’s literally the job of the distribution until they’re faced with their limitations, be that licensing (flatpaks are basically the perfect way to have closed source applications if you need them), manpower to maintain said projects, or time to keep said projects polished and well maintained (in order to avoid other Linus moments™).
Those are the main problems of encumbering package distribution to the distro maintainers, and the other big problem is f r a g m e n t a t i o n; seriously, try convincing a software developer to support linux when there are dozens of packaging formats depending on the distribution, the best you’ll ever get is either a .deb or a .rpm, flatpaks (and not snaps, because those are stupid) are an easy, surefire way to get an universal package available to every single distribution.
I don’t see them as a substitute for distribution-maintained packages, but they are the best complement out there for when distros can´t maintain certain packages that are needed, and just shrugging them off like that is absolutely stupid.
They just implemented a systemd feature, systemd-oomd. To be honest, it can cause issues in some edge cases, but it works pretty well in any distro (that uses systemd).