Counterpoint: X11 wasn’t designed with today’s security needs in mind, and developers were building based on the assumptions that those security holes would remain. We don’t actually want everything that X11 had, we only want the good bits.
Or to put it another way, the switch from X11 to Wayland = https://xkcd.com/1172/
Hang on…
Just because no one has asked it yet…
Are you only using a HDMI cable and have you not tried a display port cable?
FYI: The “HDMI Forum” didn’t want to allow open source implementations of HDMI 2.1. They wanted to charge people a fee for using it. This is why people use display port, it has no fee and it usually has newer feature support earlier.
I think some of the downvotes might be annoyance at not knowing what servo is.
Everyone in the web and rust communities would know that it is the original rust application that the rust language was made to create: a new web browser built with memory safety and safe parallel execution as first concerns.
Parts of it ended up in Firefox then servo died when Mozilla fired a whole swath of their own devs.
It was stuck in limbo for a few years but has seen a revival under Igalia who have a history of fixing bugs and supporting/adding features to the existing browsers which the big players don’t have the resources or the will to work on.
I do think every project needs a non-marketing-speak description of what it does on every major page that a user might visit (e.g. Homepage, project readme, releases/downloads page), but I wouldn’t really call version 0.0.1 a proper release.
Sort of.
They basically said they didn’t know about the issues with hyprland, they recently looked into them and to them in looks like hyprland has changed enough to be supported.
But, they were silent on the DHH. That part is the serious concern.
Hyprland is the project associated with Transphobia. To put it delicately, the original developer was so cringe to the point that others didn’t want to work on the project.
DHH is the developer who is associated with White Supremacy, as he started making overtly white suprematist comments on social media.
Supporting Hyprland definitely looks like a mistake, they weren’t aware of what went on around there.
They probably should have gone with supporting Niri and maybe Cosmic instead.
Gotos being bad falls in the it depends category.
Bad:
Good:
I don’t see any actual temper lost here.
In one case he points out that someone is making commits that have messed up a file’s indentation, and to stop doing that because it’s messing things up (they were).
In the other case he points out that rust’s default format rules are wrong (in the context of version control readability, they are) and asks someone to fix them.
I’m more interested in what the Oil shell has been doing, it has a higher potential roof while keeping backwards compatibility rather than the current standard of affairs 10ish year development cycle of a new shell with slight improvements.
Switching shells can be a massive pain in the ass, so if we’re making a change, it has to be worth it.
Oil looks like it could be worth it and then some.
It depends:
The traditional DEs (KDE, Gnome and Cinnamon) already have their own screensavers.
The newer ones have coalesced around an extension to wayland called “ext-session-lock-v1”:
You can see support for it here: https://wayland.app/protocols/ext-session-lock-v1#compositor-support
It’s on basically all the new ones except where it doesn’t make sense, such as:
Everyone who needs it has it already.
There will probably be an ext-session-lock-v2 and get pulled into the traditional DEs at some point, but probably after a whole bunch of getting everyone around the table and in agreement on some security questions: how do we prevent malicious software setting themselves as a screensaver for a screenjacking attack?, what happens when the screensaver crashes?, that kind of stuff…