Readit NewsSwift has (had?) the same issue and I had to write a program to illustrate that Swift is (was?) perfectly happy to segfault under shared access to data structures.
Go has never been memory-safe (in the Rust and Java sense) and it's wild to me that it got branded as such.
Keep in mind there was a point where I was vegan, I know several vegans, so I know what I’m talking about.
They’re not shy about it either—look up That Vegan Teacher on YouTube for relatively middle-of-the-road vegan behavior in action.
Handling thousands of concurrent requests is table stakes for a simple web server. Handling thousands of concurrent processes is beyond most OSs. The context switching overhead alone would consume much of the CPU of the system. Even hundreds of processes will mean a good fraction of the CPU being spent solely on context switching - which is a terrible place to be.
They go remote, but don't change a lot of other things or attempt to mitigate the downsides (there are downsides, everything is a trade off) and then claim its a failure when they need a stealth layoff.
Also IBM has a long history of "Resource Actions" so this type of thing is not all unexpected from them.
Wiz is a SaaS b2b startup. Even on a forum for startups most people haven't heard of them.
Wiz reportedly has a revenue of 750m. It would take Google 30 years or more to break even on this deal. But like all bs startups Wiz will fade into irrelevancy 6 months after being acquired.
Google is getting completely scammed.