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
-
-
To me this means serverless is just, for most people, a JS flavor of a particular kind of PaaS. Your definition fits Heroku+Rails.
-
Intentionally so (if you autoscale) Why shouldn’t it? You could also add “no RAM shared by requests” but that seems very slippery+unhelpful.
-
Right, so I agree with this, but the thread yesterday had people contorting themselves to explain why its *new*.
-
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.
-
I would like to make clear that at no point did I argue it was anything new:-)
-
Yeah it mostly wasn't you :) I think it's useful to see "serverless" as a continuation of Heroku + shared-nothing. Name sucks as a result.
End of conversation
New conversation -
-
-
When you say "never" – fine, not until the term popped up – but then they did it all the time.pic.twitter.com/M2ipKZTvn3
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
