frankfurt_schoolgirl

frankfurt_schoolgirl, 6 months ago

I mean xwayland is the best supported X implementation today, and will only get better. You’re not ditching everything when you maintain backwards compatibility.

frankfurt_schoolgirl, 6 months ago

I’ve been using Wayland for 5 years. There were a few bugs in the beggining, but now it works great. These threads are such a waste of time.

I have over 100 confirms X11 developments

That’s great dude. Why don’t you go maintain it then, apparently nobody else wants to: www.phoronix.com/news/RHEL10-Removing-X.Org

Wayland took too long

Look up how long btrfs has been in development, or at audio subsystem churn. These things take time, because it’s mostly volunteers working on them.

Systemic complexity has doubled in the last two years

What does this even mean?

Mir was better

It turns out the Canonical dumping random stuff over the wall is not the same as creating a legitimate open source community around a project.

Unfixable amount of race conditions

As if there’s never been a synchronization bug in X… But also System76 and others are writing Wayland compositors on Rust anyway.

frankfurt_schoolgirl, 6 months ago

I think that it’s a great project, and I hope it succeeds. My sense is that there is more momentum around Nix, so for a lot of uses it just makes more sense.

Guix and Nix both have the same issue imo, which is using a loosely typed language with an odd syntax. I feel like something both strongly typed and with a more common syntax would be easier to edit and faster to evaluate.

frankfurt_schoolgirl, 7 months ago

You need to update your inputs so that you’re using the 23.11 branch of nixpkgs instead of the old one. In my experience, a couple of things will break, but there’s usually warnings about it.

frankfurt_schoolgirl, 7 months ago

yeah if you’re using unstable than it’s rolling release and you just need to update regularly. the point releases shouldn’t matter too much