“Lambda and serverless is one of the worst forms of proprietary lock-in” (2017)

Re:“Lambda and serverless is one of the worst forms of propr... by jasonkester on Tuesday February 05, 2019 @06:26AM (#19084359)

We're using the definition a few notches upthread: "Dear manager, for the next weeks/sprint the team needs X days to upgrade the software to version x.x.x otherwise it will stop working"

As opposed to:

2011: deploy website, turn on windows update

2011-2019: lead life as normal

2019: website is up and running, serving webpages, and not part of a botnet.

That's reality today, and if it helps to refer to it as "maintained", that's fine. The point is that it's preferable to the alternative.

[ Parent | on HN ]

Re:“Lambda and serverless is one of the worst forms of propr... by nostrebored on Tuesday February 05, 2019 @06:38AM (#19084408)

I think that the parent commenter is referencing node 4.3 being past EOL and being unmaintained software and therefore unfit for prod, unlike the ms stack which is receiving patches

[ Parent | on HN ]

Re:“Lambda and serverless is one of the worst forms of propr... by akoncius on Tuesday February 05, 2019 @08:05AM (#19084903)

https://en.wikipedia.org/wiki/.NET_Framework_version_history begs to differ.

[ Parent | on HN ]

Re:“Lambda and serverless is one of the worst forms of propr... by marvy on Tuesday February 05, 2019 @09:51PM (#19092281)

node, not .net

[ Parent | on HN ]

Re:“Lambda and serverless is one of the worst forms of propr... by akoncius on Monday February 11, 2019 @05:20PM (#19138947)

I was referring to comments that MS is good at backwards compatibility and “if you write application, it will run forever” and I pointed out that MS also breaks backward compatibility what regards languages.

[ Parent | on HN ]