Hacker News new | past | comments | ask | show | jobs | submit login

Why is everyone here so upset about the word "serverless"? It's exactly what it says: You aren't responsible for maintaining any OS or server. That's it.



We are upset because we're being told that it is serverless, then there are clearly servers anyways.


No need to dig into the weeds or wax poetic on the term, people call it serverless because you, the user, don't have to manage any servers personally when you use the "serverless" application.

It sounds like the dislike comes from folks here who just want to be contrary is all.


So by that definition, facebook, linode, shared webhosts, GCE, etc.. are serverless. AirBnB is homeless. Uber is automobileless.

Ok, maybe I'm not being contrarian, maybe I just like semantically useful and intuitive technical terms instead of blatantly wrong and misleading ones? Maybe the problem is that I care about my field of expertise and don't want it to be further watered down by the perpetual sloppiness of "who cares, it's just a name"?


I feel like I'm repeating myself, but serverless means you don't care about servers when running your code At all. That's it. Your examples above don't fit into that at all, so they aren't really applicable.

You submit your job, function, whatever and it...just runs. You don't have to worry about servers, hence the name. Not sure why everyone feels like arguing over a simple concept, but alas.


> but serverless means you don't care about servers when running your code At all

We already have semantically useful terms/naming conventions for that. Shared Host, Cloud hosted, $LAYER-as-a-Service, etc.. No need to use a blatantly misleading term instead.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: