So what, that's just an API they expose. Great dev experience. OpenWhisk let's you do the same thing, editing functions in browser. But remember for anything beyond that, with Lambda, you upload a particularly structured zipfile 
I bet internally there are all kinds of strange reasons Lambda is built the way it is. I can only speculate. But I don't think the arch of the go runtime makes what I said obviously false.
-
-
I'd also guess a similar internal debate to what we are having happened. "long term business goals" vs "dev ux" vs "we needed Go support yesterday!"
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I think the fact that they architected it so that you're just uploading a binary – and then just open source the function-API library, shows that they're happy with no lock-in on the code side.
-
Thats fair. I don't think "run my code" is about lock in. it's ensuring a future where Lambda can be more valuable and better optimized than it is today.
-
Totally agree – and if they ever do release a Docker runtime for Lambda, it'd come with some restrictions for sure – or at least, "if you go beyond these restrictions, then cold boots could be slow"
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
I do realize they can be much more, but you just described so many containers.
It'd be the same business model as Lambda is right now