[lukasLansky]

As much as I like the described move from "functions" to "containers", solutions like KNative / Cloud Run are still inherently more hackable than solutions like Fargate.

It's good to have properly defined, stable, open interface for compute workloads (containers as defined by OCI), so we don't have to lock ourselves into whatever shape of runtime environment our current cloud provides for their flavor of FaaS. So we don't have to learn cloud-provider-specific tooling, getting certifications for handling various tasks at AWS, becoming 2010s variants of Cisco-certified network engineers of the previous age.

But it's even better to have a properly defined, stable, open interface for orchestration too. To be able to run stuff locally. To be able to extend things. To ease the lock-in cloud providers currently have. To be able to actually understand what happens under the hood. And last but not least: to enable rise of open source solutions for higher-level abstractions, like KubeDB.

[k__]

Funny that both sides has its gripes with Fargate.

For a serverless proponent like me it's still too much config.

For a no lock-in proponent like you it's not enough config.

[StavrosK]

The way to satisfy both camps is sane defaults.

[shabda]

“A good compromise is when both parties are dissatisfied”

[jjoonathan]

A bad compromise leaves both parties dissatisfied, too.