In case you haven’t heard the news, Framework went and publicly sponsored Hyprland (the most toxic part of Wayland by a country mile) and openly shilled Omarchy multiple times (the pet project of fascist shithead David Heinemeier Hansson) recently.

In response to well-justified backlash against this, founder Nirav Patel responded with FOSSbro platitudes about “[creating] a big tent" for open source”.

If you’ve got any more updates on this self-inflicted shitshow, put them here so they can be collected in one place.

(In retrospect, that AI-pilled Framework Desktop should’ve been a major red flag they were gonna pull this shit.)

EDIT: Found a solid summary of the situation in the wild - recommend checking it out.

  • Seminar2250@awful.systemsEnglish
    5·
    2 days ago

    I guess there’s sway? none of these options entice me to be honest

    I used to use Sway. I found it tedious to configure several different things via config files. Kanshi in case you plug in a monitor, Waybar, Swaylock[1], etc. And, I may be misremembering, but you had to edit the Sway config to launch these programs at startup. There was just friction everywhere.

    I have been daily-driving COSMIC for about six months and it works pretty well, although there are infrequent crashes (less so since the beta release, I think). I like it as my tiling WM, but also occasional crashes don’t affect my workflow too badly.

    Wayland protocols are an almost ideal way to create intentional incompatibilities and network effects.

    Would you be willing to elaborate or follow up on this? I checked out the core protocol but think I’m way too out of my depth to relate it to what you wrote.

    1. Also there was a bug that allowed people to bypass your lockscreen by mashing keys. Sort of made me hesitant to try anything Sway again, although I believe the problem has been fixed. ↩︎

    • self@awful.systemsEnglish
      6·
      1 day ago

      for Wayland, the issue is unfortunately outside of the core protocol. the core protocol doesn’t implement everything you need for a functional desktop, and some of the omissions are utterly obvious things. the ecosystem makes up for that with protocol extensions, but some (all?) of the important ones are proprietary to a particular compositor and considered part of its internal API. also, because Wayland has a frankly pretty broken security model (everything is utterly locked down and as far as I can tell no exceptions are possible via permission modals or any other mechanism), some types of applications are only possible via fragile hacks. gnome has many of these proprietary protocols because Wayland is essentially under the same umbrella and so it has a privileged position; KDE is in a close second. every other compositor has severely reduced functionality.

      for more details, see jwz’s recent blog posts where he failed to port xscreensaver to Wayland because some of the utterly basic functionality he needed was compositor-specific. the hyprland wiki’s compatibility page is also relevant because all of those problems tend to be rooted in this too, though I of course don’t recommend trusting them as a source. Asahi Linux also has a ton of issues on their github around hyprland that I believe boil down to protocol issues. unfortunately these issues tend to be hidden from public view because they’re spread out across a hundred rants and a hundred discussions in FreeDesktop’s Wayland protocol committee; a properly formatted Mastodon search might also be informative.

      (counting down the seconds until some Wayland dev wanders in and tells me I’m completely wrong about everything because an uncharitable reading of one of the paragraphs above reveals I’m wrong about some minor point and besides what am I saying, everyone should be on xlibre? toxic little fucks)

      • self@awful.systemsEnglish
        4·
        1 day ago

        I collected some mastodon links so you know roughly what to look for:

        • here’s a game developer unable to do window positioning, multi-monitor, display type detection, hi-DPI… in portable ways on Wayland. window positioning in particular bites game developers hard, and is still unfixed for, gonna be honest, horseshit security reasons.
        • this entire thread is kind of an excellent summary
        • screen recording on Wayland sucks, and what’s interesting about that thread is the smug person replying gets it (to my memory) wrong, portals for screen recording are a hack
        • in fact here’s the post where Ariadne told me I was wrong about portals; it’s also a good starting point if you want to see what protocol discussions look like
        • here’s one of the jwz threads out of many

        in conclusion: how dare I. don’t I know these are just poor, mostly corporate-backed volunteers