[dreamdu5t]

Serverless was never a thing. There are servers, whatever you want to call the them.

Observing coworkers spend weeks setting up serverless stacks, for not needing a server they sure spent a lot of time configuring their tools...

But obviously the next thing is codeless, which is WYSIWYG all over again. Kind of like how serverless was the cloud all over again.

[setr]

Ofc there are servers; the point is that its server-independent — and ofc theres a setup and configuration to it: certain ideas still have to exist somewhere, if its no longer implicitly known by your server

What’s the point in being pedantic about the marketing naming? If you’re going to lay critiques, don’t swing wildly at the first thing you see; you gotta hit ‘em where it hurts (eg as always, most codebases don’t need that kind of scaling; the code architectural benefits can be had without buying into k8/docker entirely; auto-scaling always offers the risk of a surprise high bill; limited to short-lived functions; server configuration replaced with cloud services/docker configuration; etc)

Who do you imagine you’re trying to convince? A first year cs grad? Your mother? Does you really believe anyone who could make claim to an informed opinion would be so dense as to never think “wait! There must be something underlying all this magic!”

Serverless is not really serverless! And cloud is just someone else’s servers! Have got to rank amongst the most commonly useless statements in tech; it convinces no one and is pure signalling

[wolframhempel]

Thank you :-)