Tesla's Dojo supercomputer is DOA – now what? (theverge.com)
1 points by CharlesW 12m ago 1 comments
Deep Dive into Advanced N8n Node Development (intelda.ca)
2 points by swengcrunch 31m ago 1 comments
Please Don't Promote Wayland
42 PKop 45 8/13/2025, 1:06:22 AM stoppromotingwayland.netlify.app ↗
That said, what you need to know about Wayland is that the X.org devs mostly migrated to it en masse because they said X had hit an evolutionary dead end and couldn’t be dragged into the present, by the design of it. These were the people who were already maintaining X and presumably liked it. I doubt there were a lot of haters in that crowd.
It’s not like someone invented Wayland and shoved the X devs out of the way. The X devs largely became Wayland devs because they believe it’s the better path forward. I don’t really know how I could argue against them.
- https://gitlab.freedesktop.org/xorg/xserver
- https://gitlab.freedesktop.org/wayland/wayland
It's not just that developers migrated to a new project. Wayland is essentially the successor to X and is developed by the same group.
(That doesn't mean there aren't still lots of bugs and sharp corners.)
I didn't know or care what was pushing the pixels on my Debian install, since it works. Being Debian, it could go either way: some of the desktop environments are committed to Wayland while other desktop configurations only work under X. (Incidentally, I checked. My setup uses Wayland.)
> It’s not like someone invented Wayland and shoved the X devs out of the way.
They sure make it sound as though X application developers are being shoved out of the way. I don't understand their argument though. Most modern software is built upon libraries that support either Wayland or X (assuming it has a GUI), so they should be blissfully ignorant of whether their application is running under Wayland or X. Most of the outliers are older programs that are built on top of libraries that haven't been updated for Wayland, but most of those programs will work under Wayland assuming that xwayland is installed. Again, there is no reason for the developer to concern themselves with the distinction between Wayland and X. That only applies to a relatively small subset of outliers that are interacting with X or the compositor directly. But you're not going to escape that problem, because you're either doing something unique or you are doing something you shouldn't be doing.
No comments yet
And some of the points are really questionable, like claiming “Color management becomes inconsistent” when X11 doesn’t even support HDR, claiming that Linux containers and namespaces somehow mitigate X11’s security issues (that’s not how it works!), and talking about some outdated issues like NVIDIA support and SSH forwarding (both of which shouldn’t be an issue anymore from what I’ve heard).
Though the real pain points for me have been around the various containerization things that just cause things like my IME to barely function.
At least Python 3 if you started your project on Python 3 you mostly could just get where you wanted to be.
Currently I can SSH from my MacBook/XQuartz onto an Ubuntu/Linux system and run xterm (or whatever). How does that work in the future?
And Martin Fowler article on Strangle Fig pattern.
It's been a waste of resources to have yet another biffurcation on the Linux Desktop ecosystem.
It's pretty sad.
And of course window managers like i3 needing complete replacement, but those seem to be mostly down already.
Like this feels super bleeding edge and in that case I really don't get how this didn't _start_ in x11 land and then take over things from there.
My only hope is that money from people who "need" linux graphics to work solves this.
Wayland is the Project Xanadu of UI software.
I get it that some people don't want give up the old systems in favor of the shiny new technologies. I'm also on that side for some software like systemd (not debating. Systemd does offer many compelling benefits). But this article feels like complaining for the sake of it, rather than making reasonable detractions that could perhaps be addressed in Wayland. Attacking a software for just existing isn't a good strategy in FOSS. It is fundamentally about having choices.
Wayland fragmented development efforts on Linux. It's gotten a little better as some compositors consolidate, but still pretty awful to cobble together a stack that works for the features above.
I see the development advantages of Wayland, but not the practical advantage as a user. And even as a developer, X11 is stable and well known (albeit definitely weird in places).
At the end of the day, things worked perfectly on X11 and my audio and video and various apps still glitch a lot on Wayland even after all these years. Most of that is not exactly Wayland's fault, but it highlights the advantage of X11. It's the devil you know (and everyone has worked out a lot of edge cases for).
Everything under the "security" section of this article is so unbelievably wrong, that I'm not sure if it's worth anybody's time to refute one by one.
Stuff like global hotkeys sounds unfun tho
> The XLibre project continues this legacy with active community development.
Guess what? Nvidia users also "face particular challenges", and many normal hardware configurations simply don't work reliably under XLibre either. I guess Linus was right, don't use Nvidia.
These complaints remind me of how Linux was criticized more than a decade ago for not not being compatible with proprietary applications, while foss applications worked just fine on proprietary platforms. While technically correct, it misses the whole point, seemingly rather intentionally.
[1] https://x.com/probonopd/status/1955387873659850828
>What We're Losing
>1987-2024: X11 Evolution
>37 years of continuous development, bug fixes, and feature additions. Stable, predictable, and extensively documented. The XLibre project continues this legacy with active community development.
This is a very charitable interpretation of the situation, and to suggest XLibre, which got forked 2 months ago, is the future is insane. Would be a different story if XLibre had been around a few years but 2 months is very young..
Wayback is the more promising project, if you can run an X11 display manager on Wayland you can still do XRDP and SSH, is my understanding. Those are the two features i really depend on
One guy.
> Training Overhead
> $5,000-$15,000 per IT staff member for multi-compositor environment training
When's the last time your IT department gave you "multi-compositor training"?
> Software Replacement
> $500-$2000 in software replacement costs when tools don't work under Wayland
> Multi-Monitor
> X11: Reliable, consistent behavior
> Wayland: Compositor-dependent, often buggy
> Distro wars intensified: Choice of display server becomes a major differentiator
Definitely written by AI
These days in many places supporting the differently abled legally is on the way out, but I still think it's a good thing. And yeah, the dollar figures smell, but this is a real problem that the waylands introduced by not being a single wayland. One that has so far only been addressed by GNOME in their compositor by introducing two entirely new acccesibility protocols with no support for the last 30 years of accesibility.
If you want to actually be following the guidelines of American's with Disabilities Act of 1990 this might matter to you.
The ship sailed when Keith Packard, brilliant programmer and X.org project lead, decided that the era of X11 is over, and no further development will happen to the Xserver, and that the rootless Xserver for Wayland, in the near future, will be the only actually supported version.
This lead to the weird fork of Xlibre that is more about politics than it is about technological solutions.
Everyone has chosen to abandon the security nightmare that is X11, somehow it took 15 years instead of 5. But hey, we finally made it.
I don't care, I'm saying it. Fuck your fragmentation whining. USERS WANT THEIR SHIT TO WORK. They expect high refresh monitors to work. They expect to be able to use a fking external monitor alongside their hidpi laptop. They need to be able to use actual fractional scaling, again with varying dpi monitors.
They want their shit to work reliably and not tear. Wayland delivers on this. Now. In a way X11 never EVER will.
God Jesus fuck i cannot believe how much people's time has been wasted on this bullshit useless banal conversation.
There's so much wrong with wanting or thinking an XScreensaver app would somehow work with a random Wayland compositor. But it does require ignorance of the exact security changes made to the model when moving from X11 to Wayland.
I can't. I can't. I should never waste my time in these threads.
Edit: i do also find it amusing how much of that manpage is dedicated to calling out how fragile and broken X11 is. You can't make this stuff up.
Edit2; I actually can't get over the irony of linking an app that notoriously has had a storied history because of X11's architecture. I can't name the number of time X11 sessions were not locked properly.
Whatever. Going to keep happily enjoying the basic features that every other desktop OS user expects that I get with KDE, gnome, cosmic, away, Niri, and more, in Wayland. Good luck unclutching y'all's pearls.