> Trying to abstract this away behind a CLI seems like it misses the ethos of Lua.
With `lx add <package>`, you can install the package and add it to und config file in one step. And do things like fail if the package or version doesn't exist or isn't compatible with your system.
You can provide editor plugins or use LSP to give users hints if there's an update available, and use code actions to update them, etc.
> It’s also a tad strange that a package manager designed for Lua isn’t written in Lua.
Again, the fact that Lux relates to Lua is a pretty weak argument for choosing Lua as a language to write or configure it in.
Lots of Lua libraries and packages aren't written in Lua, but are built with Lua bindings.
Lua (which as you yourself just mentioned was conceived as a configuration language) is a pretty poor choice for something with the scope of Lux.
In fact, luarocks was recently rewritten in Teal.
Lux has a Lua API (lux-lua) which means it can be embedded or used as a Lua library.
> Presumably Lua developers already have Lua installed, know Lua, and would more likely contribute to a project written in Lua.
We're not worried about finding contributors. If anything, what we need are high quality contributions. Lua developers who only know Lua are not what we're looking for.
That alone is a pretty weak argument.
> Trying to abstract this away behind a CLI seems like it misses the ethos of Lua.
With `lx add <package>`, you can install the package and add it to und config file in one step. And do things like fail if the package or version doesn't exist or isn't compatible with your system.
You can provide editor plugins or use LSP to give users hints if there's an update available, and use code actions to update them, etc.
> It’s also a tad strange that a package manager designed for Lua isn’t written in Lua.
Again, the fact that Lux relates to Lua is a pretty weak argument for choosing Lua as a language to write or configure it in.
Lots of Lua libraries and packages aren't written in Lua, but are built with Lua bindings. Lua (which as you yourself just mentioned was conceived as a configuration language) is a pretty poor choice for something with the scope of Lux. In fact, luarocks was recently rewritten in Teal. Lux has a Lua API (lux-lua) which means it can be embedded or used as a Lua library.
> Presumably Lua developers already have Lua installed, know Lua, and would more likely contribute to a project written in Lua.
We're not worried about finding contributors. If anything, what we need are high quality contributions. Lua developers who only know Lua are not what we're looking for.