I found https://wayland.app/protocols/ very helpful so far.

That and studying smithay code.

That was the documentation with the incorrect nullability I was referencing.

I doubt there is anything incorrect there. See the note here: https://wayland.freedesktop.org/docs/book/Message_XML.html#a...

wayland.app just HTML-renders the contents of the specification XML files. If a compositor or client is not interpreting nullability the same way wayland.app says it should be interpreted, then that's a bug in the compositor or client.

What if no compositor is interpreting it correctly? We tested on Weston, GNOME (this was shortly after it went Wayland-only) and Plasma and the same problems persisted on all 3. In all fairness, the exact functions with wrong nullability might have been different, I don't remember, but the nullability issue itself was persistent on all 3.

What's needed beyond API docs is a review, refresh, and possible merging of the two Wayland Books by active Wayland contributors.

https://wayland.freedesktop.org/docs/book/ https://wayland-book.com/

Because it was explicitly advertising Rust and you can't stand the zealotry or because you hate Rust?

Because the latter is really dumb. I don't mind a software written in C, although I personally wouldn't want to write it anymore.

Interesting... Need to check how this differs from agdb, with which I had some success for a sideproject in the past.

https://github.com/agnesoft/agdb

Ah, yeah, a different query language.

This hype too will pass. It's always ebb and flood...

> One thing I’ve noticed is that different people get wildly different results with LLMs, so I suspect there’s some element of how you’re talking to them that affects the results.

Which is Fortuna's work... stochastic models are like that. And confirmation bias is another phenomenon as well as "how do LLMs align with my worldview" whether I see them more positively or more negatively.

Someone has worked too much on corporate Java Codebases.

I feel your pain. Everything is so convoluted that 7 layers down you ask yourself why you didn't learn anything useful...

Last time was a go shop, and let me tell you: that style mixes with go's error handling like spoiled milk and blended shit.

Oh gee, thank you for this wrapped error result, let me try to solve a logic puzzle to see (a) where the hell it actually came from, and (b) how the hell we got there.

Corporate has the magic touch to do that to any programming language.

All it does is generate soup. Some of which may taste good.

There is no thinking, no matter what marketing tells you.

I just told my dog he isn't allowed to post here anymore...

He said he will take his business elsewhere then!

The question I ask myself to this day is why they began switching to React. It made no sense at all for me. Like it was a working product, so why would you switch?

I get that new developers might be more familiar with React, but then again, as soon as the trade-offs were apparent, I would've pulled the plug.

But they said: Buckle up, everyone, let's ruin our product!

Promotion-driven development happens at Microsoft just like any other big tech company.

Hm, I didn't realise they'd moved to React. I remember reading years ago that it used jQuery for the longest time but they put in some effort to move to pure Javascript (maybe using web components).

Yeah, right. I mean, I'm so happy that only one of my clients is using GitHub as their GitForge. Every single other one hosts their own GitForge. And I can't state how much better every single other GitForge is.

GitHub was the pinnacle of GitForge a couple of years back, and it seems like they wanted to hit a wall.

Otherwise, you cannot explain how you can enshittify a software that much.

There was GitHub, and then it was Microsoft.

Microsoft trying to run a Ruby on Rails + SSH + Git system.

Exactly. But given all the slop, not even just AI slop, I wonder how Microsoft can still be in business.