build inlang binary file on sqlite

[samuelstroschein]

⚠️ not to confuse with building lix on sqlite

Context

Dropping the "inlang files should be stored in git" requirement opens the possibility for a binary inlang file.

Proposal

Build the inlang binary as zipped file (or lix archive file) that stores Bundles, Messages, and Variants in SQLite.

project.inlang
- settings.json
- db.sqlite <- bundle, message, variant

Pros

• persistency, queries, locking, all out the box. we don't [re-invent a database for inlang](https://docs.google.com/document/d/1Cx8HUWnVdaZF_rwGwRbCt8HUtXaJF5TSwkR8yDDdUeA/edit?usp=sharing).
• lix is forced to build plugin api that can merge inlang files

Cons

• change history needs longer to implement because slot files are dropped in favor of lix change api

Timeline

1 week rebuild @martin.lysk1's sdk v2 on sqlite

1 week sqlite reactivity

---

2 weeks assumed effort

Questions

Why is lix is forced to build plugin api a pro?

We get faster to third party lix plugins/file formats/developers the faster we have the plugin API.

How would the developer workflow look like?

Nothing changes for developers. See this loom

Strategy Shift Towards Binary Inlang File 🔄

[samuelstroschein]

Will be implemented