Just keeping a single frame buffer image can take tens of megabytes nowadays, so 100MB isn't all that much. Also 64-bit can easily double the memory consumption, given how pointer-happy the ELISP data structures can be (this is somewhat based on my assumptions, I don't actually know the memory layouts of the different Emacs data structures ;)).
But I don't truly know, though. If I start a terminal-only Emacs without any additional lisp code it takes "only" 59232 kilobytes of resident memory. Still more than I'd expect. I'd expect something like 2 MB. But I'll survive.
A patch contains more than the changes: it contains the commit message. In open source projects, and in particular in CVE fixes, the commit message can indeed be quite descriptive. It needs to be!
You're still right, though. But I like to think professionals are able to verify the changes with the high-quality commit message—possibly in less time than investigating the issue themselves.
I doubt there would be a measureable benefit: after all, the kernel is already compiled without 32-bit support, and the code related to it just doesnt exist in the resulting binary. I assume there could be some small exceptions, though, like choosing to do something in a certain way so that the same approach will also work for 32-bit, and opting for another approach would perform better in 64-bit. That's just a guess, though.
It's mostly about maintenance load.
Btw, with PAE the host can have more than 4 GB of memory, so the limit would only apply to individual processes. Still quite feasible to use that kind of system even in the modern day--even if the browser can sometimes become quite large.. And then there are of course the numerous embedded applications.
I think I could easily enjoy the gesture, however it's way too easy to trigger. It's like a one centimeter movement on a tablet. E.g. the Android app switcher needs a much bigger movement to trigger app closing.
Do share if you have experiences using yabridge with the flatpak distribution of Bitwig! My existing setup did not work with that, but the deb version worked ok on Debian, so I keep using that.
yabridge works really great for working with Windows plugins. I have quite a few of them working out just fine—at least with Bitwig, which is a native application.
That said, I've also seen some plugins that did not work. In particular the problems can be related to license management; they probably get confused of what kind of system it is running on..
In my view yabridge is easy to use, but on the other hand I have a decent amount of Linux experience, so perhaps the experience can vary.
One other thing is that you can bulk create your own instances, and that's a lot more effort to defederate. People could be creating those instances right now and just start using them after a year; at least they have incurred some costs during that..
I believe abuse management in openly federated systems (e.g. Lemmy, Mastodon, Matrix) is still an unsolved problem. I doubt good solutions will arrive before they become popular enough to attract commercial spammers.
In other words, if all the billionaires just ceased to exist, it would result in the humanity achieving the emission goals?