News for hackers. Stuff that matters.
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service... by mattrjacobs on Monday October 29, 2018 @02:27AM (#18325433)
Every single comment here is about the name “serverless”. Can’t actually think of a better bikeshed example than this.
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service... by kbenson on Monday October 29, 2018 @02:36AM (#18325463)
Just coming to this article, I find my self agreeing with you and the gist of the thread about serverless being a horrible descriptor at the same time.

It was just one thread though, and I could see how it sucked people into its vortex, I haven't even had a chance to read the article yet, and here I am doing the same as everyone else (including you...). Well, worse actually, as we've contributed to a new thread.

Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service... by bryanrasmussen on Monday October 29, 2018 @05:56AM (#18326171)
Considering that all we have in that shed is a bunch of tools for the county workers maybe it shouldn't be called a bikeshed.
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service... by rasteau on Monday October 29, 2018 @03:42AM (#18325650)
"[T]he English language... becomes ugly and inaccurate because our thoughts are foolish, but the slovenliness of our language makes it easier for us to have foolish thoughts."
Re:Why Netflix Rolled Its Own Node.js Functions-As-a-Service... by EngineerBetter on Monday October 29, 2018 @02:54AM (#18325507)
I find it easier to live with if you consider it to mean "daemonless". So not about hardware, but what software you don't have in your project.