The Lua community needs to learn to move on

24 points by tusharhero


dualvariable

An open source project trying to provide support for 10-year-old versions is just crazy.

They need to be working on their dev branch and backporting fixes to their last released version for maybe a year--then cutting a new release and dropping support for N-1. Anything else should require support contracts.

Users don't understand how abusive it is to expect support or backwards compatibility for 10-year-old versions, when there's no corporate giant behind funding all the work.

Open source maintainers should not be internalizing a requirement to do that, and should just reject it and aggressively drop support.

technomancy

Would be a lot better article if it gave like ... actual reasons?

bitshift

I understand that Lua is an embeddable language and if you make a decision in a point in time to bundle, say Lua 5.2 in your app and you build a plugin ecosystem around it, then you’re married to it forever. But then that’s your app’s ecosystem to take care.

If I were in Mike Pall's place, I'm not sure I would go so far as to delete Git tags for previous versions, but I would be thinking very much along the lines of, "Do you have a support contact?"

Jan200101

We should really be (gradually?) moving into supporting only the latest PUC-Rio Lua and the latest LuaJIT, at best.

YES, I've been saying this to people for YEARS but the biggest hurdle for all of them is, as mentioned, their ecosystem breaking apart over such changes.

mro

Curb your expectations.

P.S.: I like lua for what it is.