The Road to Zynx 1.0
As Zynx continues to evolve, we are formalizing our development path toward a stable 1.0 release. Zynx is currently a labor of love maintained by a single developer, and our mission remains clear: to provide a systems programming language that combines the safety of modern semantics with the raw performance and portability of C.
Community involvement is the catalyst that will transform Zynx from a promising prototype into a production-ready reality. This roadmap outlines our three-phase strategy to move from our current state to a stable ecosystem.
Phase 1: The Path to Alpha (2027)
Our immediate focus is on stabilizing the core language and refining the developer experience. The Alpha release will represent a feature-complete foundation for early adopters.
- Feature Stability: Finalizing the core semantics of ownership, borrowing, and generics.
- Standard Library Definition: Architecting the
stdlibmodules for essential system operations, I/O, and data structures. - Integrated Tooling: Delivering the official built-in formatter (
zynx format) and language server. - Multi-Source SDK Installation: Implementing a robust system for installing SDKs from various official and community-maintained sources.
- Documentation: Launching "The Zynx Book," a comprehensive guide for idiomatic development.
- Diagnostic Excellence: Refining compiler errors to provide educational, actionable feedback.
Phase 2: Advancing to Beta
The Beta phase will shift focus from language design to ecosystem growth and production readiness.
- Library Ecosystem: Streamlining the creation and consumption of third-party libraries.
- Static Compilation: Ensuring first-class support for fully static, zero-dependency binaries.
- Native Debugging: Finalizing C++ ABI mangling compatibility to enable seamless debugging via
gdbandlldb. - Performance Benchmarking: Establishing baseline performance metrics against modern systems languages.
Phase 3: The Journey to 1.0 Stable
The final push to 1.0 is centered on reliability, verification, and long-term architectural stability.
- Decentralized Package Management: Implementing a secure, Git-based dependency model that supports project, user, and system-level installations.
- Ecosystem Stability: Ensuring the project management tools and package registry mechanisms are robust, predictable, and stable for long-term use.
- Exhaustive Verification: Expanding our integration test suites to cover edge cases in memory safety and generic monomorphization.
- Platform Parity: Guaranteeing stable support across Linux, macOS, and Windows with consistent ABI behavior.
- API Stability: Committing to backwards compatibility for the core language and standard library.
Join the Journey
Zynx is currently developed and maintained by a single person. While the vision is ambitious, collective effort is what will accelerate our timeline toward a stable release. We invite you to follow our progress on GitHub, contribute to the standard library discussions, and help us build the next generation of systems programming.
Your contributions - whether code, documentation, or feedback - are what will make Zynx a "real thing."
