I like this refinement of the definition.
"Serverless" postdates LXC and Docker so "easy to sandbox" can't be the distinction, right?
-
-
i think it’s that you can avoid process startup overhead and may even not need to fully sandbox at the OS level
-
You still need to sandbox because JS isn't useful without some exposed OS guts and security is hard ;)
-
My hypothesis is: 1. Serverless is, more or less, definitionally about JS 2. It's popular because JS is popular and empowering
-
I think the extremely fast startup time of a container running node was crucial to the order of magnitude change I mentioned.
-
You could have done it with PHP but as you say JS (and node) are more popular with the up-stack devs this appeals to.
-
i think the time to market for a serverless JS offering is also just way shorter, because of status of embedding hooks as 1st class citizens
-
I don't understand this argument.
-
i just think JS was the prime language to pioneer the serverless space, all the way from the implementation to the community
- 2 more replies
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.