myng111

Out of curiosity, what was the reason you chose to do this rewrite? Was there some issue with GLFW?

From an infrastructure PoV, I seem to recall that WhatsApp was one of the few major companies that used Erlang, and were famous for being able to run the entirety of WhatsApp on only a few servers, each of which was serving millions of concurrent connections, mostly thanks to Erlang/BEAM (at least, from what I read). When it got acquired by Facebook, they then proceeded to rewrite the entirety of the backend in C++. Seems kind of baffling to me.

I suppose the theory is when you're attacking a console like the Xbox One with some known hypervisors vulnerabilities, but generally what is considered to be secure hardware, you could use the patchable hypervisor vulnerability to install your custom OS, then use the OS itself to find silicon bugs, finally securing a pathway for permanent access to the device.

It's fascinating how fast the Forgejo I host at my university's laboratory loads from my home network. Every page load is <100ms. I think it goes to show how much bloat we don't realise exists in modern webapps.

Certainly tcc. Probably also rui314's chibicc as it's relatively popular. sdcc is likely in there as well. Among numerous others that are either proprietary or not as well known.

I'm interested what these DOS applications are running on. Is it virtualised or a real physical machine?

Did 7zip not support tar files before? Or is POSIX tar a particular standard that was not previously supported?