• drspod@lemmy.ml
    link
    fedilink
    arrow-up
    28
    ·
    1 year ago

    I started the video thinking “huh, that’s neat I guess” and then I was more and more impressed as the video went on. This would be pretty revolutionary in how it could change your workflow. It’s the kind of feature that would get me to switch from Gnome to KDE if it was only supported fully in the latter.

    • macallik@kbin.social
      link
      fedilink
      arrow-up
      12
      ·
      1 year ago

      Very similar experience. He did a good job of building to the “Ok but why does this matter” aspect of it all

  • shockwave@kbin.social
    link
    fedilink
    arrow-up
    22
    ·
    1 year ago

    It’s not just about crashes. You can switch compositor without logging out or save save the full state of an app to disk to ‘sleep’ the app if you are short of memory. I’m sure people will think of other possibilities too.

    • andruid@lemmy.ml
      link
      fedilink
      arrow-up
      19
      ·
      1 year ago

      I’m a big fan of high availability software rollouts. It would be interesting to see this do a live update where you spin up the new compositor, run some test on it, if it passes hand off, if that succeds kill the old one. Minimal disruption for the end user.

      Kind of neat for desktop users, but for kiosks or other always running GUIs its super cool to me

  • Vincent@feddit.nl
    link
    fedilink
    English
    arrow-up
    10
    ·
    1 year ago

    With all the Linux on mobile work, one thing I was wondering about is how Android (and iOS too, I think) can just stop apps running in the background if it thinks they won’t be opened any time soon, to save energy, and how apps must therefore be programmed to be able to handle that gracefully. There has been a lot of focus on making apps adapt to the screen size, but not so much on making them save energy like that - I wonder if this work could enable that in one go for whole classes of apps?

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    arrow-up
    8
    arrow-down
    2
    ·
    1 year ago

    It’s a nice feature in theory. In practice, the sort of crash this guards against happens to me no more than once a year. Often more rarely. And I’m including all my machines in this anecdata - my personal desktop, laptop, corporate workstation, with Intel and NVIDIA GPUs in the mix. 😄

    • Sh1nyM3t4l4ss@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      1 year ago

      In addition this feature makes debugging and developing KWin much easier because you can just restart the compositor without interrupting your workflow.

    • macallik@kbin.social
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      In the video he provides additional use cases outside of crashes. If I’m understanding it correctly, one is the ability to seamlessly transition across and/or run multiple DE’s in real-time, and the second is reimagining app loading by being able to restore apps from the disk as if they never left RAM. Someone please correct me if I misinterpreted this

      • Avid Amoeba@lemmy.ca
        link
        fedilink
        arrow-up
        6
        ·
        1 year ago

        Hahaha. You know what, I thought that’d be the case but I’ve been on Wayland on my Framework since Ubuntu 20.04 LTS and I’m baffled at the stability of the stack. I thought it’d be a shit show, and it wasn’t. I guess a decade of development didn’t go in vain. 😄

  • patatahooligan@lemmy.world
    link
    fedilink
    arrow-up
    4
    arrow-down
    2
    ·
    1 year ago

    This would be an incredible QoL improvement for gaming, at least until all compositors reach feature parity. Imagine using your preferred compositor for everyday tasks, quick-switching to another one that supports VRR and/or HDR while gaming, and then back again, all without logging out and logging in again.

  • TeryVeneno@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    There was also a talk at GUADEC that discussed this exact feature but even more fleshed out, I believe for GNOME. It was reminiscent of iOS or Android’s sleep and resume capabilities for apps.

    • Rustmilian@lemmy.worldOP
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      1 year ago

      X11 is a mess and unmaintained, it’s a huge ask. Assuming it’s even possible on X11.
      Besides, Wayland is literally X12.

      • PseudoSpock@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        1 year ago

        X11 didn’t have to be abandoned, that’s my point. And nothing is “X12”, as Wayland doesn’t do a lot of what X11 did. Calling it “X12” is propaganda.

  • PseudoSpock@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    1
    arrow-down
    5
    ·
    1 year ago

    @Bro666@lemmy.kde.social See that? Someone else dissing on “the fiasco” known as KDE 4 within the first 30 seconds of their excited statement about the upcoming KDE Plasma 6. You want to rush over there and call them rude? Want to rush over there and proactively ban them from your joke of a KDE lemmy channel and instance that cannot tolerate feedback? You stood up for KDE 4, “Bro”… you’re on the wrong side of history. Now, go do your wounded pride thing and tell him to go code it for himself. Go on. It’s your one move.

  • dingdongitsabear@lemmy.ml
    link
    fedilink
    arrow-up
    3
    arrow-down
    8
    ·
    1 year ago

    are you making stupid faces in your video thumbnails? couldn’t care less what you have to say, not clicking ever, plenty info elsewhere.