Skip to main content

2 posts tagged with "lingua franca"

View All Tags

· 3 min read
Tassilo Tanneberger
Marten Lohstroh


Programming languages like Python, Rust, or JavaScript are popular not only because of particular language features, but also thanks to the quality of the tools and packages they offer access to. A good and mature ecosystem includes features such as developer support, mainly through IDEs or LSPs. Lingua Franca already shines in this area with its VSCode integration that offers functionality like code highlighting, error handling, build support, and diagram synthesis. Another important aspect of a modern language's ecosystem concerns package management. Although it is possible to import reactors from files in the local file system, support for packaging in Lingua Franca is still in its infancy.

The Lingua Franca team is therefore pleased to present Lingo, a new package manager and build tool for Lingua Franca. While we still have a long list of features that we want Lingo to have (including the ability to publish packages), you can already do quite a few useful things with it. For instance, you can easily set up new Lingua Franca projects with lingo init --language, which creates a Lingo.toml and a small hello world program under src/Main.lf. The Lingo.toml specifies a set of apps that are executable LF programs. Apps can be configured with additional build and target properties.

name = "Showcase"
version = "0.1.0"


name = "Main"
main = "./src/Main.lf"
target = "Cpp"
platform = "Native"



To build this app, simply run lingo build and Lingo will start building all the apps specified in the Lingo.toml. You can then find your build result in ./target/bin/Main or simply run lingo run if you want to execute the result. The command lingo clean is available for cleaning up build items.

Lingo uses an internal concept called backends to wrap the different tool chains of targets. At the moment there is a CMake (Cpp), pnpm, npm (Typescript) and a lfc backend, but the lfc backend is a temporary solution until a backend is written for all the different toolchains. Therefore, it is important to know that not all targets and functions are officially supported yet. Especially the creation of federated or embedded programs is not yet supported.

We highly encourage the use of Lingo as it already improves the quality of life when developing LF applications and gives us valuable insights into the needs of developers. But you may be wondering how you can get Lingo. Lingo is published on To install it, simply run:

cargo install lingua-franca

and lingo should show up in your $PATH. If you have a question, problem or bug, please submit a issue here.

· 2 min read
Marten Lohstroh

We have a new website! Most importantly, this website is the home of our documentation.

After careful consideration, we realized that our original website had become overly intricate to maintain due to its numerous customizations and dependencies. Writing comprehensive documentation is already a challenging and time-consuming task, and we were keen on avoiding additional complexity that could hinder our progress. Additionally, we had a wishlist of new features, including the ability to version our documentation, incorporate a blog page, and provide support for MDX. In pursuit of solutions, we explored various options.


Fortunately, we discovered a framework that encompassed all the features we desired: Docusaurus. The adoption of this framework allowed us to streamline our infrastructure significantly. Remarkably, we were able to retain essential functionalities, such as our Algolia-based search bar and Markdown-based documentation pages, which are now more accessible for reading and editing.

Despite initial reservations about the switch, particularly the prospect of rebuilding LF-specific functionalities—such as support for multiple target languages and Lingua Franca syntax highlighting, which demanded a considerable investment of time and effort - we were pleasantly surprised. Docusaurus-native features like Tabs and Tab Groups, coupled with existing third-party libraries like Shikiji, seamlessly resolved our concerns with minimal adjustments. This not only addressed our specific needs but also considerably eased website maintenance.

We hope that you like the new look and feel! If you have any comments, corrections, or other suggestions for improvement, feel welcome to create an issue here or submit a pull request here.