it’s trivial to restrict access to file system and other OS functions, which makes it safer to run other people’s code in your environment
-
-
it’s been a feature of the language from day 0, as opposed to Ruby/Python/etc which aren’t designed for running untrusted code
2 replies 0 retweets 1 like -
Heroku has used Linux sandboxing facilities to implement this concept for ages: https://12factor.net/processes (Heroku apps are 12 factor)
1 reply 0 retweets 1 like -
"Serverless" postdates LXC and Docker so "easy to sandbox" can't be the distinction, right?
1 reply 0 retweets 0 likes -
i think it’s that you can avoid process startup overhead and may even not need to fully sandbox at the OS level
1 reply 0 retweets 0 likes -
You still need to sandbox because JS isn't useful without some exposed OS guts and security is hard ;)
1 reply 0 retweets 1 like -
My hypothesis is: 1. Serverless is, more or less, definitionally about JS 2. It's popular because JS is popular and empowering
5 replies 3 retweets 18 likes -
Trying to explain "serverless" as new obscures the simple fact that millions of developers who know jQuery can write backend logic.
1 reply 0 retweets 5 likes -
The same thing that made Node popular, but with the added benefit of getting back to the ease of ops that PHP had a decade ago.
3 replies 0 retweets 6 likes -
That is a very insightful observation.
1 reply 0 retweets 3 likes
Aw shucks.
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.