I've seen a few serverless projects that are really, really jacked up. 1000s of functions glued together with little intentional design... basically one big pil

I've seen a few serverless projects that are really, really jacked up. 1000s of functions glued together with little intentional design... basically one big pile of spaghetti code. Things like the Serverless framework[1] help, but ultimately today's serverless architectures feel like they forgot Dijkstra's warning: that the "Go To Statement Considered Harmful." [2] I'm still big on the approach for the right use cases: variable work loads are a good example. But ultimately, to be truly useful, we need to see either a) better coupling with non-serverless approaches, or b) a "serverless 2.0" approach that builds in the good parts and fixes the bad parts. (But please don't call it serverless 2.0... those of us who lived through "Web 2.0" will thank you) [1] https://www.serverless.com/ https://www.serverless.com/ [2] https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.pdf https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.p...