4 ms·
Off topic, but the "serverless" moniker needs to die. I propose "adminless" as in "server I don't have to admin, configure, or patch" as being much more descrip
by le-mark 9y ago
Off topic, but the "serverless" moniker needs to die. I propose "adminless" as in "server I don't have to admin, configure, or patch" as being much more descriptive of whats really going on.
- motoboi 9y agoWell, it's not adminless either, as AWS have lots of them keeping the hosts alive and running. But if you can ignore that, you can probably also ignore the fact that your code runs on a server.
- nathancahill 9y agoEh, if I'm deploying a cloud function, the server truly doesn't exist for me. It's more like a Web Worker running in a privileged environment. I'm ok with the name.
- sidlls 9y agoNo, it's really a server running your function. You just (are told you) don't have to worry about the server or what it's actually doing.
- dvfjsdhgfv 9y ago> You just (are told you) don't have to worry about the server ...until you receive the $206 bill for the work done by the server.
- nathancahill 9y agoBut that works on the VPS level too. We're just talking about higher levels of abstraction on top of hardware. Which one stops being a "server"? I'd argue that once you lose the OS, it's no longer a "server".