Yes. Do you know what deploying in my local environment, for my own projects, is? It's "control-S". (Because a file watcher reloads the application.)
This is acutely top-of-mind for me because I used to run a devops consultancy and I currently head devops, including release management, for a startup built heavily on AWS Lambda. I am doing my level best to reduce the loop as much as I can for the dev team.
It's still way, way slower than control-S. And always will be.
What is it that makes this a problem? It has literally never been an issue for me.
I test the lambda body locally with a single command. Only upload a new zip when you hit the release candidate stage and that's not frequent enough for the few seconds it takes to upload to lambda to be a problem.
This is acutely top-of-mind for me because I used to run a devops consultancy and I currently head devops, including release management, for a startup built heavily on AWS Lambda. I am doing my level best to reduce the loop as much as I can for the dev team.
It's still way, way slower than control-S. And always will be.