• 0 Posts
  • 5 Comments
Joined 2 years ago
Cake day: June 29th, 2023
  • lastweakness@lemmy.worldtoLinux@programming.dev•New Rule Forbids GNOME Shell Extensions Made Using AI Generated Code
    1·
    3 days ago

    You’re literally looking at a post that is a result of that effort… The human review process exists to try and reduce GNOME Shell extensions that could potentially break the shell. The link I posted details other steps as well, but of course you didn’t bother reading that. And again, it’s impossible to never break extensions because extensions are just scripts that monkey-patch the GNOME Shell process. Trying their best is all they can do.

    With how Reddit and Lemmy react to GNOME, you would think GNOME killed their dog or something.

  • lastweakness@lemmy.worldtoLinux@programming.dev•New Rule Forbids GNOME Shell Extensions Made Using AI Generated Code
    1·
    3 days ago

    The medium post is mostly about bugs (it’s software, that happens, report them or patch them) and distribution packaging issues (they seem to use Manjaro, so makes sense). Then it talks about design inconsistencies and all, which basically every Linux desktop is worse than GNOME with. Then it uses lines of code as a metric? Then it uses memory and compares GNOME to less capable desktops and ignores that KDE’s memory usage is not too far away. I’m sure there’s a lot of legacy code everywhere though.

    I don’t know what to say about Felipe’s issue since he wants a behavioral change in a library and he’s mad that the GNOME devs aren’t making that change.

    That said, all these desktops rely on GNOME components, so idk why they have such an attitude specifically towards GNOME. It’s just software, don’t get too heated over it.

  • lastweakness@lemmy.worldtoLinux@programming.dev•New Rule Forbids GNOME Shell Extensions Made Using AI Generated Code
    1·
    4 days ago

    Of course there are extension devs who left GNOME due to the lack of a stable API. But they were all looking for something that was inherently not possible with how extensions work in GNOME. I can’t blame them, “extensions” is a misnomer in this case after all. It’s actually more like userscripts being applied on a web page in a browser.

    If possible, take the time to read the link in my earlier comment, it should clear up a lot of misunderstandings about “GNOME devs intentionally breaking extensions” as most people seem to think of it as.

    Given how extensions work (monkey-patching), it’s actually really impressive that most extensions haven’t really broken since GNOME 45 and the steps taken by GNOME to that end are impressive. Even the human review being discussed here is part of that, it’s exactly because an extension can literally bring down a user’s shell (also similar to how a web page can crash due to a userscript), so they’re trying to reduce the chances of that happening.

    GNOME has always had a bit of a communication problem. They’re working on it. But I promise you, they’re all wonderful folks trying their best, even if they fail to convey that well sometimes.