IHeartBadCode

I mean I’ve been trying to formally request that ISO change the C API for send() to yeet() for sockets where connection reliability is not required at the network interface level.

Maybe I’m not Rusting enough.

Wayland development. Tons of folks yelling “X is good enough!” Where they just ignore that no one is actively developing XOrg which is pretty much the biggest X11 implementation.

Plenty maintaining XOrg but new things aren’t coming to XOrg, there’s just no one there the XOrg devs moved to Wayland.

So all these people shouting, they’re telling you keep a piece of software that’s very fragile, in a space that hardware makers are progressing at rapid pace, has decades of hot fixes, duct tape, and cruft, and nobody is actively developing for.

Like I just don’t understand the people yelling that Wayland is raping peoples wives and setting fire to their dogs. The yelling group is screaming for people to use something that nobody wants to work on and nobody is paying enough for people to work on. The code base is horrible and it easily causes burnout in three weeks or less. No one in their right mind is picking it up for shits and giggles.

So if everyone abandons Wayland, what’s the end goal? Keep riding XOrg till hardware outpaces it completely? Like I don’t understand what the Wayland haters are trying to get at. There’s so little going on in XOrg at this point and everyone seems to universally hate the code base. And a rewrite of the base sounds a whole lot like Wayland but artificially adding in X11 restrictions that make no sense since we all aren’t using PDP-11 to run the clients.

I get that Wayland has configurations that don’t work yet. All software has bugs, including X11 implementations. But Wayland is arguably a technology that is more in line with how modern hardware works than the X11 protocol will ever be. And Wayland is designed to be easy for devs to work with, not a cobble of archaic limitations due to a protocol that was designed for 1970s era computers.

That level of hate for Wayland is just this confusing Luddite cry for software that hardware that properly supports it no longer exists. The reason modern video cards do run on X at this point is because of a lot of hacks. I thought everyone understood this when we did the whole AIGLX vs XGL thing.

Next hardware reset and automatic reorientation for Voyager 2 is October 15th. Yes the device automatically resets itself about four to five times a year. Communications are expected to be reestablished then.

For anyone interested. Here’s a video of programming an EEPROM with dip switches and using it to drive a seven segment display.

The guy’s channel also includes how to build a very simple computer using various ICs. If breadboard computers are your kind of thing.