My hypothesis is: 1. Serverless is, more or less, definitionally about JS 2. It's popular because JS is popular and empowering
-
-
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 -
I think ease of ops is key. To me, serverless means “managed, auto-scaling PaaS”. App Engine counts I think. Not about JS.
1 reply 1 retweet 2 likes -
But app engine never called itself serverless and is oooold. Suddenly a "serverless" movement popped up and ppl are convinced JS pioneered
2 replies 0 retweets 1 like -
Replying to @wycats @sophiebits and
To me this means serverless is just, for most people, a JS flavor of a particular kind of PaaS. Your definition fits Heroku+Rails.
1 reply 0 retweets 0 likes -
Intentionally so (if you autoscale) Why shouldn’t it? You could also add “no RAM shared by requests” but that seems very slippery+unhelpful.
1 reply 0 retweets 0 likes -
Right, so I agree with this, but the thread yesterday had people contorting themselves to explain why its *new*.
1 reply 0 retweets 2 likes -
Replying to @wycats @sophiebits and
I agree that by any reasonable defn it's not, but the fact that people so badly want it to be can't be ignored.
2 replies 0 retweets 1 like -
Replying to @wycats @sophiebits and
Which is why I speculate that serverless is a similar phenomenon as node: empowering jQuery devs to write backends, now with 0-ops!
1 reply 0 retweets 0 likes
Which is a huge, huge deal. Not to be underestimated.
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.