Yeah, I imagine there's some QT bits for implementing a lot of it, if it detects them being available. Not being massively familiar with QT or how those two apps make use of it, I can't assume they'd be making use of the components that'd implement KDEs custom extensions. So you know shrugs

I mean many Wayland compositors is kinda like old browsers at the moment. They all implement a common spec and then implement a bunch of their own extensions to get features the spec doesn't allow for. And apps have to be aware of these custom extensions to make use of them. So in the KDE case, I imagine a lot of their apps are aware of KDEs own extensions to Wayland. But it doesn't mean all of them are.

People who find success can, sometimes, become arrogant and become blind to other factors contributing to their success. Just enough failure can keep you humble. Pretty typical human reactions.

Does it, if you can work on the normal application code, there's no reason you can't work on the lower levels of applications. It's all just code. Ramp up might take a bit more time, but I wouldn't expect horrendously so. As long as your patterns make sense and what is there is written well enough and is not a spaghetti monster in the making, any one should be able to pick it up.

Time to go back to email lists. Anyone can come along sure. But it's only going to be the most determined.

Fair enough. I don't tend to use it all that much. But it is there. I tend to find I don't really need to see the graph all that much. Maybe because I'm mostly working in small teams. It's just not that important to my understanding of what's going on.

Right, but I don't see a 'and you can feed it to a neural network on demand such that it can reproduce code that a user can then have plausible deniability that it was licensed on a certain way and be able to redistribute it under an incompatible license"

git log --all --graph

I would have thought that you fix it locally, git commit, and regenerate the patch set again. Maybe with optional squashing of commits so each patch set doesn't keep growing.

I don't think the code is the problem they are cleaning up. I think they just want to remove the contributor from the history.

I mean it should. It'll have a steam os installed on the device itself. It'd be a pretty silly oversight to not work with a computer running Linux.

It is. Relatively so. This smells of Mozilla wanting to package things in there that Linux distro maintainers wouldn't package in themselves.

You may say I'm being overtly cynical and as much as I love Firefox, I can't say I trust Mozilla's intentions