Web Development

I mean, I've seen a growing number of companies looking for Salesforce; it's even worse (all of your code only works on their platform because it's a proprietary language AND they charge for things as absurd as how many lines of code you have).

A lot of the things that you can't do with serverless expressed in this article are not things you want to do on a web server anyways. Like writing a temporary file, sharing state in process between requests, or spawning a thread.

Sure for a truly small workload where you don't have to worry about abuse and scaling beyond one machine you can get away with that stuff. However, for companies that do need to be able to deal with multiple machine workloads and don't want to worry about hiring a team of engineers to implement a scalable cloud or run their own physical hardware in a data center ... I think serverless likely has some value.