Nope. We chose TOML as the default for various reasons:
- Simplicity.
There are use cases for a turing complete configuration language.
Lux is not one of them.
- Ergonomics.
The ability to edit it using the CLI (technically, that could be possible with Lua too, but it would be a lot more complex and not a very pleasant UX).
> which, I don't know if that's the right call?
The reason we currently support importing a Lua extra.rockspec is ease of migration for complex projects, e.g. with platform-specific overrides (not yet supported by the TOML spec).
Nope. We chose TOML as the default for various reasons:
- Simplicity. There are use cases for a turing complete configuration language. Lux is not one of them.
- Ergonomics. The ability to edit it using the CLI (technically, that could be possible with Lua too, but it would be a lot more complex and not a very pleasant UX).
> which, I don't know if that's the right call?
The reason we currently support importing a Lua extra.rockspec is ease of migration for complex projects, e.g. with platform-specific overrides (not yet supported by the TOML spec).