Opral Company Update September 2024
TL;DR
While lix is not releasable, the perceived progress is incredible.
Re-alignment of the team that lix is the new primary focus.
8-week plan to hit lix 1.0 and have “put your company in lix” demo
The August company update stated the goal to release the inlang SDK in v2 and pre-release lix. While neither has been achieved, the perceivable progress of lix is incredible, and we re-alignment that lix is the new primary focus.
Lix had more progress over the last 8 weeks than the last 24 months combined
The progress is incredible. Here is a presentation that I gave to the team a week ago:
lix now supports multiple file formats
fast iteration SQLite WASM foundation
Why was the goal of releasing the inlang SDK v2 and apps not achieved?
Too much at once.
The ambition to release the lix SDK, inlang SDK, and apps, with pressure to release all three in August, led to parallelization. Parallelization in a situation where every app depends on the inlang SDK, which in turn depends on the Lix SDK. If anything in the lix SDK changes, the inlang SDK needs an update. If the inlang SDK is updated, all apps are required to update.
Dependencies coupled with parallelization meant that every team was constantly undergoing refactors, which, due to the dependencies, needed to be communicated with other teams. The result was dependency hell and friction.
All resources are invested into lix until v1 is out.
The release of inlang v2 is postponed until lix v1 is out.
Lix 1.0 till the end of the year
I will take over lix to push 1.0 out until mid-December.
Milestone for