Its crazy to me how this lines with cloud engineering so much. The phrase was “data has gravity” because the further the data is from the processing the more you have to spend to move it around and the more latency you’ll get from it

Even the idea of ECS has so many parallels to kubernetes declarative model and various actors within it.

Debt. Though honestly I’d ask my extended friends if they wanted to a down payment on a house first.

I don’t think anyone is stuck renting but if I could fix that in a day I’d check with everyone

I do feel like putting an intentional, obvious, but non-issue causing bug in a code base now. Make a contrib guide. Mention needing to read the docs first and check previous issues/discussions first, and make a closed ticket explaining that that bug is nothing but an example bug and that will ban anyone that attempts to fix or report it.

Like a green mnm test for a code base

Git-lfs go brrr I hope

Different definitions of capitalism make this debate a mess tbh. State capitalism would be a antithesis to description you provided but tauntalogically capitalism.

Corporatism is also clearly a type of capitalism but as corporate monopoly increases markets observably become less free and private ownership is constantly challenged by rent seekers.

I really don’t understand why this gets so complicated. Like don’t we all just make a micro service when ever we make a job or proccess in a project, and then slap those in a namespace and behind a service on k8s when you want to expose it out to the cluster, and ingress for the world?

If that gets complicated, then you refactor just like any other code base, and debug it like any other multi threaded app. Make sure actions are atomic. Functional programing helps a lot too, cause you know streaming vs stateful, but you can have stateful stuff in k8s.