mrcjkb

That's a neat suggestion, thanks. Lux will need some time to become mature, but building a large multi-platform project like koreader would definitely be a nice goal.

With Lua, it becomes near impossible for a program like lux to edit the manifest.

For example, how would I `lx add <dependency@version>` if the `dependencies` table might be generated by a Lua function?

1. The commands, `lx run` and `lx lua` will set the `PATH`, `LUA_PATH` and `LUA_CPATH`. And there's a `lx path` command for setting those environment variables.

2. It defaults to using pkg-config to detect Lua installations and will fall back to installing Lua via the `lua_src` and `luajit_src` crates if it can't find them. We may eventually add support for other tools like vcpkg.

3. Not yet. It's on our roadmap to add support for that to our lux.toml/dependencies spec, but we probably won't allow rockspecs with that to be published to luarocks.org, because we don't want to be the reason people publish packages that can't be built by luarocks.

Thanks :)

Good point. I guess that's one of the limitations that comes with a structural type system.

From the post: "I’m aware of typed languages that compile to Lua, but here’s a native approach."

Regarding teal specifically: It currently doesn't support union types as described in the post (see the 'Current limitations of union types' section of the tutorial: https://pdesaulniers.github.io/tl/tutorial.html

I wouldn't really see using hydro power in Europe as being "green". Yes, it's renewable, but the installation capacities are pretty much exhausted, and have been before there was any significant share of renewables. So by cutting a deal with a hydro power supplier, you're only displacing another consumer who will possibly start using coal, and not doing anything to support the growth of renewable energies.

Smells a bit like greenwashing to me...