Lemmy account of natanox@chaos.social

  • 25 Posts
  • 296 Comments
Joined 1 year ago
cake
Cake day: October 7th, 2024

help-circle






  • You’re in a rather special position regarding the extensions in this case because except for 3 of them, they’re all directly maintained by your distro of choice. Which, additionally, is super slow with updating due to focusing on getting Cosmic ready and therefore extremely stable (and outdated) given nothing changes. Distro-specific extensions really are one of the few places where this kind of unstable extension system makes sense, since your distro maintainer also controls the update flow of Gnome for you and can do proper QA on it w/ those extensions before making updates available. It’s not a mix’n’match of code.

    Also, I do realize that theming on Gnome isn’t officially supported on an OS level, and I don’t fully understand it all, but I do have a fairly consistently-used custom theme installed using Gnome tweaks. GTK3 iirc.

    Modern Gnome applications using libadwaita instead of GTK3 or 4 will happily mostly ignore those, and the “User Themes” extension you need on modern Gnome to enable theming likes to cause problems. Usually one of the first “recommendations” you’ll hear when Gnome starts misbehaving is to disable your themes as Gnome just does not want to have them. I was just straight-up told to “not use Extensions if you want a stable system” (after losing about 40 minutes of work, again).


  • I had some debates with Gnome devs about it which I primarily take my points from. One of them told me they actively decided against an API, for the mentioned reason.

    Looking at some old screenshot, before I cleaned out a lot in an attempt to stop the crashing I had these (don’t know which ones were still active when it crashed the third time, I only know it was about 7 to 8 and that I immediately began looking up how to install KDE out of frustration).

    • Dash to Dock
    • GSConnect
    • Media Label and Controls (Mpris Label)
    • Net Speed (definitely deleted this one later)
    • Next Up
    • RebootToUEFI
    • RunCat
    • Tray Icons: Reloaded (This is a freaking technical necessity)
    • TwitchLive Panel (definitely deleted this one later)
    • UPower Battery
    • User Avatar In Quick Settings
    • User Themes
    • Wifi QR Code

  • As far as I am aware of, Gnome went “this is it by default, want more customisability - here is API, install or write your own extensions”

    Not even that is true. They do not provide an API (specifically decided not to due to “extension developer freedom”), but allow Extensions to monkey-patch code in. That’s why it becomes unstable due to Extensions instead of just the Extension (or at least the Extension process) crashing. Imagine every change in KDE being a KWin script, or Firefox still relying on monkey-patching instead of the extension API. It’s wild.

    Meeting criticism of this absurd way of doing things in something as important as the graphical shell with “it’s FOSS so either contribute or shut up” mentality some people show here is just dumb.


  • You guys are incredibly lucky then. I ran about 7 to 8 extensions and had the whole shell crash 3 times on me over a time of a few weeks, making me lose progress. The journal logs weren’t helpful, the gnome-shell just crashed and bailed.

    GNOME only makes it possible to make Extensions via directly patching shell code and refuses to create an API. They can say whatever they want, this way of doing things is inherently unstable and will always break at some point, and it’s not primarily the fault of extension devs or users if that happens given there literally is no other way of doing it. Even something as simple as the RunCat extension is potentially able to crash your whole desktop. This is comparable to every single modification you do in KDE being a KWin script (that settings window does have a warning in front of it for a reason). Another comparison: This is also similar to how Firefox did Extensions until they adopted the common extension API in Firefox 3 (?), before then that browser was known to be crashing a lot and become sluggish quickly since any extension was monkey-patching code into it - exactly what Gnome extensions do to work.

    It’s one thing to have a clear design idea, but Gnome took away so many freedoms (even basic theming) while merely providing an absolutely ridiculous way for even the smallest customization to then blame users and extension devs when something breaks or becomes unstable. It’s no wonder people are upset. System76 outright began to work from scratch, meanwhile Linux Mint is providing libadapta as drop-in replacement for libadwaita to patch basic theming features back into programs that use it.

    If Cosmic drops its version 1.0 and keeps its promises I’d bet a lot on Gnome slowly but surely declining. It does what Gnome doesn’t want to.


  • The funniest thing about this is that, according to a Gnome dev, they decided to not create APIs or anything and keep relying on extensions to monkey-patch code into the gnome-shell process to ensure “developer freedom”.

    It’s completely mad. I uninstalled Gnome after it crashed on me multiple times, taking either my work or (once) my game process with it.

    On KDE at least IF the shell crashes it doesn’t cause all my programs to become unavailable too, I can save whatever I was doing. Its UI/UX is arguably a mess, but at least it god damn works reliably and doesn’t come as barren wasteland with missing base features. I would love to love Gnome, but god damn it hell no.




  • 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.