But I guess if performance isn't a critical use (or you just have so many invocations all the time in every data center that cold start isn't an issue), it's nice to be able to ~port~ copy and paste over your existing PHP code.
Their clients have very variable traffic patterns because they are in very different industries. They have traffic spikes at lunch, or at the end of every month for example:
> infrastructure must be able to scale and be resilient to accommodate various usage patterns. Whether it's a luncheon voucher transaction spike at lunchtime or a monthly batch of transactions by corporate clients
With your webhost, you have to setup and maintain the server, including patching/updating it, setting up SSL, etc.
I used to do that for side projects, but I've had too many servers, and maintaining them was a pain.
For something with high traffic, Lambda provides the instant scalability. Imagine servers autoscaling, but instantly. And again, without having to setup or maintain that.
> With your webhost, you have to setup and maintain the server
You're confusing a root server or a VPS with a webhost aka "shared hosting", where the hosting service takes care of Let's Encrypt certificates, and scheduled downtime for patching.
Moreover, there is no reason to use vendor-prefixed css without the soon-to-become standard css property. Bad code is bad code, Mozilla is not responsible to fix it.
