# Toit v2.0.0 Officially Released After Four Years The long-awaited stable version arrives following extensive community-driven development and major architectural refactoring. - **Source:** [Hacker News (news.ycombinator.com)](https://brifing.si/source/13c923cd-6d99-442b-9b8b-1181f4d8cd91) - **Published:** 2026-11-01 - **Topic:** [Software & Engineering](https://brifing.si/c/engineering) - **Original article:** - **On Brifing:** https://brifing.si/s/8eaf678c-2694-4230-bdf6-9233a4f9d574 ## Four Years of Development Toit v2.0.0 marks the conclusion of a four-year alpha phase that involved over 2,000 commits. The project underwent significant transformation, with more than 500,000 lines of code changed across 200 alpha releases. This milestone signifies a transition from experimental development to a stable, community-maintained software environment for embedded systems programming. ## Evolution of Ownership The project originated as closed-source software developed by Toitware. Following the company's shutdown in 2024, the project transitioned into an open-source model. Volunteers have since taken over the maintenance and improvement of the codebase, ensuring the platform continues to evolve despite the original corporate entity no longer supporting the development cycle. ## Defining Version Stability The team delayed the v2.0.0 release for a long time due to two primary factors: planned breaking changes and the constant addition of new features. Although the software remained stable throughout the alpha period, the developers required a clear threshold to finalize the versioning, eventually deciding to prioritize stability over feature completeness. ## Final Breaking Changes A critical refactoring milestone enabled peripheral APIs to accept pin numbers directly, removing the previous requirement for gpio.Pin objects. This specific update was identified as the final major breaking change necessary for the v2.0.0 release. By simplifying this API interaction, the team successfully cleared the primary technical hurdle preventing the stable version launch. ## Accepting Feature Iteration The development team acknowledged that waiting for every important feature to be finished was an unattainable goal. They recognized that the software will always have pending improvements, leading them to release v2.0.0 despite ongoing work. This shift in philosophy prioritizes current stability over the pursuit of a theoretical, perfectly complete feature set. ## Ongoing Development Roadmap Even with the v2.0.0 release, significant work remains in the pipeline for future updates. Open pull requests currently exist for a code formatter, compiler resolution improvements, and support for additional hardware architectures. These features will be integrated into subsequent releases, demonstrating that the project remains active and continues to expand its capabilities. ## Embedded Systems Context Toit operates within the specialized domain of embedded systems, where API efficiency and hardware abstraction are critical. The transition from requiring specific objects to accepting direct pin numbers reflects a design choice aimed at reducing boilerplate code. This evolution is typical for maturing languages that seek to balance developer productivity with low-level hardware control. ## Community Sustainability Impact The successful release of v2.0.0 after the dissolution of Toitware highlights the resilience of community-led open-source projects. By maintaining a stable codebase and clear versioning, the contributors have ensured the longevity of the platform. This milestone provides a reliable foundation for developers who rely on Toit for their embedded programming and hardware projects. ## Sources covering this story - https://toit.io/blog/toit-v2-0-0/ — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._