lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

LuaRocks probably will be the "centralised modules archive". And yes, it would be highly beneficial for any platform using Lua, not only the officially supported ones (s.a. Win32, Linux, OS X, see LuaRocks roadmap ;) for specifics). LuaRocks standardizes building modules, maybe also documenting them. Certainly downloading them. There is much hope in the air that it will prove out to be the _working_ distribution system that both LuaCheia and LuaX promised to be, but didn't deliver.

What I'd like to see / suggest to LuaRocks is a feedback system, akin to Amazon readers ratings. Give stars or even textual feedback on using certain modules. Then one could see both the official, authored descriptions and documentation, and "user community" gotchas or praise of it. In other words, don't just plan based on apt-get and alike, but based on Amazon as well.

I shall cc this to the LuaRocks mailing list.


peterhickman kirjoitti 29.12.2007 kello 10:51:

On 28 Dec 2007, at 11:34 , Asko Kauppi wrote:

Then there's the Lua 2nd tier, modules. These are in more or less constant flux, and there sure is generous overlap, and generous amount of bugs / bad designs in them. Comparisons of keeping up with Lua and Python become essentially the same if the 2nd tier is also included in the concept.

The question of the quality of the non core modules is valid but not actually a Lua/Roberto problem. It is more a community problem, I would like to see a nice centralised modules archive but given that Lua is used in such a wide variety of environments I'm not too sure just how useful this would be to everybody.

I've always seen CPAN as Perl's biggest ally but it has not held any other language back by not having an equivalent system.

The quality of the modules is the responsibility of the individual authors and the people that use them. What helps with Perl is POD and tests, by having a standard framework for these things anyone can add to the documentation and tests - providing the author is willing to accept updates.

Now a standard Lua test framework along with documentation standard and packaging would, in itself, help with the standards on the non core modules.

"Dogs bark at what they don't understand." -  Heraclitus