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
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 -
This is related to
@mikeal's post from today: to understand a popularity explosion, look to effects on amateurs not pros.1 reply 0 retweets 3 likes -
"it makes it easier for just about anyone to build backend logic" >>> "it helps a handful of Serious Apps scale to a billion RPS"
2 replies 0 retweets 2 likes -
Make Web Development Easy Again™
2 replies 1 retweet 8 likes -
To the original point of my thread though, I don't think serverless will take over because it is not a universally applicable pattern.
3 replies 0 retweets 4 likes -
many of the constraints that seem to set serverless apart from prior PaaS offerings seem arbitrary to that vendor.
1 reply 0 retweets 2 likes -
the most interesting product in this space is
@zeithq because it scales like serverless but lacks most of the constraints and feels PaaSy1 reply 0 retweets 1 like
The first time I came up against the Heroku "no local file system" constraint I whined. Now I wouldn't deploy without it.
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.