I understand the sentiment of this article, but the fact is, the space is maturing very quickly and this argument won't hold for long, if at all. I've been buil

I understand the sentiment of this article, but the fact is, the space is maturing very quickly and this argument won't hold for long, if at all. I've been building with Lambda and serverless architecture, generally, without frameworks for a couple of years now. My original impetus for building on Lambda was to simplify API development and deployment, mostly for myself and a popular open source framework I'd built over the preceding few years that had a few thousand GitHub stars and some Enterprise adoption. It was almost immediately obvious where the bottlenecks were in the development process. How do I keep track of functions? How do I deal with versioning? How do I track code and function re-use? How do I enforce best practices for function execution via API? I was in the (very fortunate) position where I had raised a modest $50,000 from Angels based on OSS adoption to pursue a broader business interest - we spoke to hundreds of customers and feedback directed us to (A) more clarity being needed around what serverless functions are, exactly, aside from cost-savings and (B) more mature tooling to manage them. The result of these conversations and our own vision for the future led to StdLib [1] (and an invitation to AWS re:invent last year!) which addresses many of the concerns around tooling / framework maturity argued here. It relies on an open source specification, FaaSlang [2] to handle API execution and treat web resources as simple function calls. I think the author and many people who are commenting here may find, that for a lot of workflows they'd like to make "serverless", we're the best option in the market. That said - this isn't for everybody, if you're micromanaging serverless workflows down to the MB of RAM, stick with what your DevOps team loves. However, if you love just writing code and shipping, and are looking to maximize your own development velocity with functions-first development and serverless architecture, we're your solution. We're the simplicity the author here has complained about the space lacking. We love any and all feedback - I'm an open book, e-mail me directly at keith at stdlib dot com. [1] https://stdlib.com/ https://stdlib.com/ [2] https://github.com/faaslang/faaslang/ https://github.com/faaslang/faaslang/