The term serverless is a tad misleading, I'll give you that but the technology got its name, not from the fact that it lacks servers but because you, the developer, don't manage them or have to worry about them, ever!
Here's a little article that might help you: dashbird.io/blog/origin-of-serverl...
Wouldn't that mean that every single webspace hoster has been "serverless" since the 90s? Because the customers won't have to manage or worry about them, ever.
Thank you for that article. I still find it confusing... I'm not a friend of buzzword bingo. A server is a server even if I can't see it. Alas, if that's what the technology should be called, I begrudgingly accept.
I wish more people would care about technology. We seem to go back into a time where computers are seen as "magic devices" doing "magic things". Sorry for being so stubborn about that.
I hear you! And while I miss having the observability I got with a traditional server, with serverless there are some benefits I just can't deny. Things like cost-effectiveness, scaling and the fact that it lets me - a front-end developer - worry about the business logic and the user experience rather than mucking about with the backend.
To each it's own, I guess :)
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.