Technically, we may consider k0s to be the limit of a decreasing sequence of container orchestrators `k8s, k3s, ... = k{x}s as x -> 0` in which case we have 8/x -> +inf
it smokes Spring in benchmarks, often by a factor of 10x or more, and on plaintext it's 50x faster than spring and even with the fastest Rust/C++ frameworks, so must be some awfully light baggage
Did Go ever make concurrency easy? Any modern language allows you to create threads (semantically equivalent to goroutines) and pass messages between them. Most of them even have high-level concurrency support such as…
Technically, we may consider k0s to be the limit of a decreasing sequence of container orchestrators `k8s, k3s, ... = k{x}s as x -> 0` in which case we have 8/x -> +inf
it smokes Spring in benchmarks, often by a factor of 10x or more, and on plaintext it's 50x faster than spring and even with the fastest Rust/C++ frameworks, so must be some awfully light baggage
Did Go ever make concurrency easy? Any modern language allows you to create threads (semantically equivalent to goroutines) and pass messages between them. Most of them even have high-level concurrency support such as…