I keep rejecting this definition of "serverless" in my head. There's just as much server, it's just that someone else owns and operates the server, and holds your data or application hostage when they want to. This thing currently called "serverless" is more like "server as a service", and creates more lock-in than what came before.
True serverless would mean a return to dumb interchangeable servers: static progressive web applications hosted by dumb static http servers (e.g. github pages), connecting to interchangeable data storage (e.g. W3C solid pods), with client-side peer to peer synchronization of data using CRDT algorithms (e.g. Automerge, YJS, ...). When I think of the word "serverless", that's what comes to mind.
True serverless would mean a return to dumb interchangeable servers: static progressive web applications hosted by dumb static http servers (e.g. github pages), connecting to interchangeable data storage (e.g. W3C solid pods), with client-side peer to peer synchronization of data using CRDT algorithms (e.g. Automerge, YJS, ...). When I think of the word "serverless", that's what comes to mind.