Back in 2005, a bug report was filed by Kjetil Kjernsmo, then running KDE 3.3.2 on Debian Stable. He wanted the ability to have each connected screen show a different virtual desktop independently, rather than having all displays switch as one unit.

Over the years, over 15 duplicate reports piled onto the original as more people ran into the same wall. And that’s not a surprise, because multi-monitor setups have become increasingly common.

The technical reason why this issue stayed open this long comes down to X11. Implementing it there would have required violating the EWMH specification, which has no concept of multiple virtual desktops being active at the same time.

The KWin maintainer Martin Flöser had said as much in 2013, effectively ruling it out for the entire KDE 4.x series. The only realistic path was through Wayland, and that path needed someone willing to actually walk it.

Someone finally did. The feature has now landed in KWin’s master branch and is set for a Plasma 6.7 introduction.

  • haverholm@kbin.earth
    link
    fedilink
    arrow-up
    0
    ·
    4 hours ago

    I understand the scepticism, it’s easy to be wary of assisted coding as a gut reaction these days. However, the programmer replied to his own merge request:

    I put roughly 200 hours into this (largely due to not being familiar with the codebase and technologies involved beforehand)

    …and I find it hard to believe a vibe coder would bother prompting his magic eightball for that long? Maybe that’s my personal prejudice against that particular set of (often wannabe) programmers showing.

    There’s also an “AI” disclosure in the original merge request that says:

    • None of the submitted code is AI generated. I wrote all of it myself (largely by copying existing code).

    • I used OpenAI Codex in the following ways:

      • I used it to generate a quick prototype to give me an idea of where to start. The prototype was MUCH more limited and I rewrote it from scratch (i.e. none of the code submitted here is from there).
      • I used it to help me with debugging/understanding some of the stuff new to me (e.g. how does a value get to QML, wayland protocols, understanding crashes, …).
      • I used it to review the code before submitting it (in addition to manually reviewing it myself). It caught a few minor issues.
      • I used it to write a “touchpad simulator” patch that I used for testing touchpad gestures (not submitted).

    YMMV on what side of vibe coding that usage falls.

      • haverholm@kbin.earth
        link
        fedilink
        arrow-up
        0
        ·
        1 hour ago

        Big caveat there that “AI” still makes stuff up out of the blue, despite being ostensibly trained on “all of human knowledge”. And this guy seems to have used its generated code accordingly to better apply his PHP skills to C++.

        You can probably tell I disagree strongly with “AI” being called “just a tool” 😛