Imagine if Oracle was adding a restrictions on what you are allowed to build with Java, that would be a more similar comparison IMO.
E.x. if you make a product that works on multiple databases, you can't show the performance difference between them.
And it apparently bears repeating: communication with a submarine using VLF/ELF is one-way. Such is not the case with a spacecraft, even if the latency sucks.
Maybe throw in a dedicated key-value store like Redis or Valkey.
Oh and maybe something S3 compatible like MinIO, Garage or SeaweedFS for storing bunches of binary data.
With all of that, honestly it should cover most of the common workloads out there! Of course, depends on how specialized vs generic you like your software to be.
it should/might/could be possible to write a snake game in something like, 30 bytes of x86 asm.
boot up real mode old school bios environment. 0xa000 is your screen, width/height with int 10.
[0] https://codevision.medium.com/running-c-snake-inside-uefi-df...
Do users still need to obtain (an obviously legal, Nintendo approved) ROM of classic OOT to use the randomizer?