Free and Open Source Software

22272 readers

24 users here now

If it's free and open source and it's also software, it can be discussed here. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 3 years ago

MODERATORS

Gaywallet@beehaw.org

alyaza@beehaw.org

109

A PHP Dev Just Solved a 20+ Year-Old KDE Plasma Problem No One Else Would (itsfoss.com)

submitted 4 days ago by Powderhorn@beehaw.org to c/foss@beehaw.org

40 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] floofloof@lemmy.ca 8 points 4 days ago* (last edited 4 days ago) (1 children)

Your Rollercoaster Tycoon example is a bit odd, since coding a whole game in assembly indicates deep understanding of what you're doing, whereas the problem with vibe coding is that it requires only the shallowest understanding. Unless I'm misunderstanding and that was your point.

There may be a maintainability issue with both, but for a different reason in each case.

[–] Penguincoder@beehaw.org 5 points 4 days ago* (last edited 4 days ago)

since coding a whole game in assembly indicates deep understanding of what you’re doing, whereas the problem with vibe coding is that it requires only the shallowest understanding.

Yes, that was indeed my point. That and being, who else really can understand the assembly coded game, compared to who can understand the AI written vibe coded app. The Dev who wrote it in assembly certainly understands it and a lot. The person who vibe coded an app...probably doesn't understand most of it.