After read the explanation of parent, I see it as certainly one of the most sensible models to build scalable and efficient software. This a great way to make

After read the explanation of parent, I see it as certainly one of the most sensible models to build scalable and efficient software. This a great way to make things: - You have N Cores on machine - You create N Threads to match, you don't "create/destroy/create/destroy", no, you already have the size of the problem set! - You assign roles, maybe just split between "heavy" and "light" - Your context switching is for computing small things on light - You do sequential code, tight loops and heavy I/O on heavy I truly wish I could do something like this on most languages (ie: is part of the paradigm/semantics). I use Rust now, and async is great but the mental model is HARD. - You don't have a easy way to split between workloads, anything could suddenly stall - When is easy to launch async/goroutines you launch them like is no tomorrow. - So, this mean I don't know what are the size of my threads or task are(could) be running without manually inspecting or assume. - I don't know, after look at async function, to know which workload is for (without inspect the code and the flow of it) (ok, in rust you can maybe infer if you are clever in the use of types to be markers... but still is disconnected to the run of the program) "container orchestrators" is like put a hammer to handle another hammer ("heavy OS + VM/DbEngines") under the pretense of being "light" and efficient, when actually this is how most software stack are: - A "heavy" DB engine - A "light" logic server that connect to it - MAYBE out-of-band processing for send emails and stuff So, the thing is, having Kubernetes or anything like put the solution too far away. I need, as developer, to MODEL that relationships and KNOW in what workloads this or that must operate. And the most fixed/predictable is it, the better.