To state the blindingly obvious: It's a perfectly valid term for what OP / the github repo refers to and your response just goes on to show that you probably don't know much about these things.
Let me spoil it to you: The cloud is also not an actual cloud, it's just someone else's server.
This seems like a very pedantic and harsh comment? I’d expect most people at HN to understand what “serverless” means, and it appears that tight integration with this architecture is the whole USP of this project, and as such I’d say the author made an excellent choice of putting it in the name: it makes it immediately clear what its key differentiator is.
These kinds of rants were popular five years ago when serverless was still new, nowadays it really doesn’t add any value and I fail to see what you’re trying to achieve here.
It’s just a term that stuck, as did many other terms, let’s just move on.
Do you also get angry that a firewall isn’t a literal wall of fire?
Correct me if I’m wrong but it’s also becoming (or maybe always has been) synonymous with edge deployment/computing as well. So instead of going througg the trouble to set up a CDN and load balance traffic you get it out of the box.
I’d say that “edge workers” etc are almost always serverless, but there are plenty of serverless architectures that are not edge (e.g. I know of more than a few ETL pipelines built entirely around AWS Lambda).
