Are there migration path for projects embedding a LUA version? Or is LUA incompatible between version?
Like if I build a plugin for a project in LUA 5.1, and the project want to migrate to 5.5, are there forward incompatibilities? Are there API deprecated for long enough to let people migrate?
As an observer I don’t understand why “once you choose a version for your project and a plugin ecosystem develop on it, you are married to this version”.
It’s Lua, not LUA. It’s Portuguese for moon, not an initialism.
You can’t migrate once you’ve got a plugin ecosystem because you’re not the maintainer of all third-party plugins, and the maintainers might have lost interest or died and used a licence that doesn’t let anyone else take over.
And in the mean time I read that there are frequent and apparently non trivial breakage on version.
Not trying to point finger since it is not easy, but thinking about the upgrade strategy of a project (or language) and help consumers of your project (and their plugin) get to the next version would help them on this issue. We have examples of languages doing this (or not). There may be more challenges for an embedded languages (than for Rust or Python) but I’m sure some concepts can still be applied anyway.
Like most names, it should be written in lower case with an initial capital, that is, “Lua”. Please do not write it as “LUA”, which is both ugly and confusing, because then it becomes an acronym with different meanings for different people. So, please, write “Lua” right!
I’ve not seen it so much with Java, but for Lua, it’s not an English word, and most things in software are either English words or acronyms/initialisms, so it’s usually a safe heuristic to assume anything that isn’t an English word should be capitalised.
Are there migration path for projects embedding a LUA version? Or is LUA incompatible between version?
Like if I build a plugin for a project in LUA 5.1, and the project want to migrate to 5.5, are there forward incompatibilities? Are there API deprecated for long enough to let people migrate?
As an observer I don’t understand why “once you choose a version for your project and a plugin ecosystem develop on it, you are married to this version”.
It’s Lua, not LUA. It’s Portuguese for moon, not an initialism.
You can’t migrate once you’ve got a plugin ecosystem because you’re not the maintainer of all third-party plugins, and the maintainers might have lost interest or died and used a licence that doesn’t let anyone else take over.
And in the mean time I read that there are frequent and apparently non trivial breakage on version.
Not trying to point finger since it is not easy, but thinking about the upgrade strategy of a project (or language) and help consumers of your project (and their plugin) get to the next version would help them on this issue. We have examples of languages doing this (or not). There may be more challenges for an embedded languages (than for Rust or Python) but I’m sure some concepts can still be applied anyway.
To support your point in stylizing the name: https://www.lua.org/about.html
I wonder why people do this. Happens a lot with Java too.
I’ve not seen it so much with Java, but for Lua, it’s not an English word, and most things in software are either English words or acronyms/initialisms, so it’s usually a safe heuristic to assume anything that isn’t an English word should be capitalised.
Look at my other reply that explains and links to it: https://lemmy.ml/post/50986115/27084875 or this link https://lemmy.ml/comment/27084875 I’m not sure which type of link to provide, same comment.