It violates the principle of least surprise. You don't expect the compiler to delete your bounds checking etc.
The way c and c++ define and use UB is like finding an error at compile time and instead of reporting it, the compiler decides to exploit it.
Back before it was awful, sourceforge required your code to be in CVS and then later svn.
Should focus on getting rid of undefined behavior.
Another benefit from working from home: I will happily spend my own money on a good chair, keyboard, etc. I spent 20 years working in an office and there's no way I would've ever brought in my own chair during that time... I would've had to become the chair police to prevent it from getting "reappropriated"
So it won't work for 0.0001% of all github projects.
Interesting. A year ago I was looking for something exactly like this for distributing data between multiple servers. Everything required a ton of overhead or was too big to use. I ended up just using json. I did discover that Brotli can compress 3 gigs of json down into just 70 megs nearly instantly.
One of our data providers gives us hundred megabyte json files. Whenever there is a problem with the data they request examples, jq is invaluable in those instances.
Interesting. I didn't realize Wayland was so extendible. I wonder if that means we can do a konfabulator clone.
There was a ton of software sourcecode posted to the comp.sources.unix usenet group that I wanted to check out. The problem is all that software was in shar format, and there was no way to extract those files on msdos. I found Yggdrasil Linux on CD at a local software store and decided to check it out. Been using Linux in one form or another ever since.
And I recommend you read Chris Latter's essay on UB.
https://blog.llvm.org/2011/05/what-every-c-programmer-should-know_14.html
Where he gives plenty of examples of UB resulting in the compiler optimizing away safety and introducing security vulnerabilities silently. In part 3 he discusses the efforts clang has made to improve on this.
He then went on to make Swift and says this: "Undefined behavior is the enemy of safety, and developer mistakes should be caught before software is in production."
and
"UB is an inseperable part of C programming, […] this is a depressing and faintly terrifying thing. The tooling built around the C family of languages helps make the situation less bad, but it is still pretty bad. The only solution is to move to new programming languages that dont inherit the problem of C."