this post was submitted on 14 Oct 2023
521 points (98.2% liked)

linuxmemes

21272 readers
426 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    521
    KDE problems require KDE solutions (feddit.de)
    submitted 1 year ago by [email protected] to c/[email protected]
    66 comments fedilink hide all child comments
     

    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

    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 12 points 1 year ago (1 children)

    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?

    [–] [email protected] -5 points 1 year ago* (last edited 1 year ago) (1 children)

    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.

    [–] [email protected] 6 points 1 year ago* (last edited 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/