The Toit v2.0.0 announcement outlines the final breaking change and expanded device compatibility.
TOIT RELEASES VERSION 2.0.0 AFTER FOUR YEARS OF ALPHA
*After more than four years of alpha development, Toit 2.0.0 arrives with a decisive API refactor and expanded hardware reach. The release signals a shift from perpetual beta to a stable, community‑driven platform.*
Toit v2.0.0 lands after more than four years of alpha development, 2,000+ commits, 500,000+ lines changed, and 200+ alpha releases. The platform began as closed‑source software from Toitware, later opened to the public, and survived the company’s shutdown in 2024 thanks to volunteer contributors. Despite the "alpha" tag, Toit has been stable for a long time, but two factors delayed a 2.0.0 label: pending breaking changes and an ever‑present wish list of features. The final breaking change—a refactor allowing peripheral APIs to accept raw pin numbers—has now been merged, clearing the path for the version bump. Developers acknowledge that feature freeze is impossible; open PRs for a formatter, compiler resolution upgrades, and broader architecture support remain in the pipeline.
What does Toit v2.0.0 change for developers?
The release replaces gpio.Pin objects with raw pin numbers in peripheral APIs, eliminating a long‑standing breaking change. A unified `toit` command now treats the language as a full‑featured desktop scripting tool. The package manager has been rewritten, fueling a growing ecosystem of reusable modules. Mixins let classes share implementations without duplication. Firmware envelopes let users tweak firmware without rebuilding the SDK. Compiler and runtime tweaks shave latency and improve error reporting. Hardware testing has been overhauled, delivering faster, more reliable validation cycles. GitHub now offers syntax highlighting for Toit source files, easing code review and onboarding.
How did the project survive Toitware's shutdown?
Toit began as closed‑source software built by Toitware. After the code was opened, volunteers took the reins. When Toitware ceased operations in 2024, the open‑source community kept the commit stream flowing, delivering over 2,000 commits and altering more than 500,000 lines of code. The project survived on volunteer pull requests, community testing, and a shared belief that the platform could outlive its corporate origin. This model proved resilient, allowing continuous releases despite the loss of a formal sponsor.
Which new hardware does Toit now support?
Version 2.0.0 broadens the hardware matrix dramatically. Support now includes the Arm‑based EC618 processor, a chip previously out of reach for the project. In addition, the SDK covers almost all ESP32 variants, closing gaps that limited IoT deployments. This expanded compatibility positions Toit as a viable runtime for a wider range of embedded devices, from low‑power sensors to more capable edge processors.
Will future releases add major features?
The team admits that the moment of feature completeness will never arrive. Open pull requests linger for a dedicated code formatter, deeper compiler resolution improvements, and support for additional architectures. These items sit on the roadmap for upcoming minor releases. The developers have signaled that each new version will layer incremental value while preserving the stability promised by the v2.0.0 milestone.
Frequently asked questions
When was Toit v2.0.0 released?
It was released after more than four years of alpha development, following 2,000+ commits, 500,000+ lines changed, and 200+ alpha releases.
What was the last major breaking change in Toit v2.0.0?
The refactoring that lets peripheral APIs accept pin numbers directly instead of requiring gpio.Pin objects.
What hardware platforms does Toit v2.0.0 now support?
It adds broader support including the Arm‑based EC618 and almost all ESP32 variants.
Toit 2.0.0 marks a turning point: a community‑driven project that has shed its alpha label without a corporate safety net. The release delivers concrete improvements—API simplification, hardware expansion, and tooling upgrades—while openly admitting that future enhancements will arrive incrementally. As open‑source contributors continue to push the codebase forward, Toit’s trajectory suggests a stable, extensible platform for the next generation of embedded applications.
Sources: [Hacker News – Toit v2.0.0 blog post]