>Operating systems/embedded applications can generally use `core`. Which doesn't, correct me if I'm wrong, provide a stable allocator API or OOM handling yet.

>Operating systems/embedded applications can generally use `core`. Which doesn't, correct me if I'm wrong, provide a stable allocator API or OOM handling yet. >E.g. games When your client pings 400 servers, how is it doing that? How is the game server implemented? >a scientific simulation That runs on one machine, and doesn't do a lot of disk IO? (concurrent file IO matters too). >even web-browsers Open the Chrome dev tools "network" tab, and then open Gmail. How many requests did it make? Again, concurrent IO is important.