KDE problems require KDE solutions - eviltoast

I know it’s called plasma, and I don’t know if it’s actually plasmas fault, don’t judge me, it’s for the meme

    • michaelmrose@lemmy.world
      link
      fedilink
      English
      arrow-up
      14
      arrow-down
      2
      ·
      1 year ago

      You mean the gnome that had a memory leak for the first 8-10 years because every frame non-deterministically allocated memory that may not be freed before the heat death of the universe which they solved by by running the GC every frame because they couldn’t fix their bad design?

      The one where the only way many people’s computer wouldn’t fall over is if they restarted their computer or gnome…

      Then they switched to Wayland and it was impossible restart the compositor without losing your apps.

      The one where common features in other environments are only available via JavaScript extensions that break every release where if even one of those teeny tiny JavaScript extensions crashes your entire gnome session crashes taking out all unsaved data and all your apps?

      That gnome?

      • 👁️👄👁️@lemm.ee
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        9
        ·
        edit-2
        1 year ago

        Someone’s very upset over gnome it looks like. Never had a memory leak on my machine, been using it for years. Gnome is fully complete, the only “common features” it’s missing are things you subjectively prefer. Like restarting a Wayland compositer is what really bugs you? What an incredible obscure problem that you’re crying about. The actually polished DE that isn’t a buggy bloated mess, that Gnome.

        • michaelmrose@lemmy.world
          link
          fedilink
          English
          arrow-up
          6
          ·
          edit-2
          1 year ago

          Gnome3 had a pretty big issue from inception in 2011 and continuing for 8 years without recognition. It’s not my fault you are young and just installed it last year. Some of us have been here a while. Some users continued to have issues all the way though 2021 and the fix is just as stupid as described.

          https://www.omgubuntu.co.uk/2018/03/gnome-shell-has-a-memory-leak-and-it-might-not-be-fixed-for-ubuntu-18-04-lts

          Now the problem is not restarting it. It’s that you can’t restart it in place without losing your apps. This means if your shell crashes you lose everything. This would be less of an issue if the entire desktop weren’t written in javascript, if it actually had an addon api, or if it didn’t load all extensions into the same javascript context as the shell.

          Compare and contrast to other systems which can survive graphic drivers crashing without dropping a session or X11 which can survive a component crash.

          It suffers from the EXACT problem that the old firefox addon ecosystem suffered from only gnome learned nothing from mozilla and its pervasively used. 83% of users use extensions despite the fact that they are so unstable all extension devs have to opt into every minor release with every extension because there is is no way to verify that the any given addon works with the new version.

          https://yoric.github.io/post/why-did-mozilla-remove-xul-addons/