Well, it is about code quality. And the same codebase should work on different hardware, which is not something that is required in downstream forks.
But it is sad to see that the driver was submitted in the past, is still actively developed and improved, but there doesn't seem to be plans of submitting them again.
Also I don't think that a platform driver is so complicated that it requires such a long time for mainlineing. It not a filesystem or VPN.
On a more interesting topic, the SteamDeck platform drivers are still not merged into mainline Linux... :'(
Last news about it: https://www.phoronix.com/news/Steam-Deck-Platform-Driver-2024
So similar to kakoune? I tried that for a while, but it was missing some features so I went back to vim/neovim.
I need to know vi anyway, because that is available everywhere (as part of busybox), so using vim/nvim for bigger systems just fits.
Or you get a message at 3 am the next day, where they apologize that they didn't made it, but that they will deliver sometime between 8 and 22 that day.
And they do that for while gaining 0 XP?
In my head canon the people are sometimes just rusty and forgetful, because even if someone lives 100 year, that doesn't mean that they will remember everything or get better at stuff. That is why I think immortal beings that live aeons, can still be surprised or tricked. Being old doesn't necessarily mean that people are wiser.
Sometimes people just need the right motivation to improve themselves.
What about Lua/Luajit?
In most scripting languages you have the interpreter binary and the (standard) libraries as separate files. But creating self-extracting executables, that clean up after themselves can easily be done by wrapping them in a shell script.
IMO, if low dependencies and small size is really important, you could also just write your script in a low level compiled language (C, Rust, Zig, ...), link it statically (e.g. with musl) and execute that.
E2E is just one part of the puzzle, you got to have a open source P2P or federated architecture as well, otherwise you have to trust a nebulous company or person intrinsically. People change and companies can be bought, but you will be stuck with their platform in order to contact your acquaintances, and changing that means loosing your contacts.
That is why the DMA is important. But you will be even better off just directly choosing a chat platform, where the users are in control.
"Corporatism vs Capitalism" was invented by capitalists to create a strawman that they can blame instead of blaming capitalism for everything wrong with captitalism.
The rest of the world uses Corporatism for something else entirely, what you might mean is corpocracy or corporate capitalism, which are just manifestations of capitalism.
To me calling someone seems rude, because the caller demands immediate time from the callee and interrupt them in what they are doing, even if it is only about forcing them to make the decision of picking up, or ignoring the call.
While texting lets the receiver chose when they want to read their message just like the sender when they want to send it. Receivers can still read the message whenever they have some time without missing anything.
Yeah, the whole article is a bit fishy:
In addition to generating clean electricity, the new ITO-silver window coating creates a cooling effect by allowing only the visible part of the light spectrum to pass inside. Other parts of the spectrum are reflected outside.
So how would a room actively cool down, when you let only the visible light spectrum inside? Sure it might not get as hot as if you let all light inside, but it will also not get colder.
Nothing of this is a burden, it is just part of being a good contributor that reads and follows the rules. Contributing is pretty easy, when you have read and are following the guides. If you haven't already, you should give it a try.
I am pretty sure that this isn't the first contribution of Valve to the Linux kernel. It sounds more to me like "works for me, don't care about others" attitude. Which is not a good attitude to have when working in any collaborative project. (Not necessarily against the developers, could also be management.)