Roadmap

Last updated: April 2026. This is a living document — priorities shift as we learn what developers actually need.

---

What Shipped in v1.11

v1.11 was the "Developer Experience Release." The goal: make developers productive in their first hour.

Language:

• enum.to_string() returns "Red", not "0" — zero-cost string tables at compile time
• for i, v in arr — indexed iteration (finally)
• "ha" * 3 — string repeat operator
• int? — optional type syntax sugar
• Missing return is now a compile error, not a warning
• Type mismatch errors come from Wyn, not the C compiler — with line numbers and suggestions

Tooling:

• wyn test — cross-platform test runner, no shell dependency
• wyn fmt — code formatter with --check for CI
• wyn build shows binary size and compile time

Numbers:

• 149 tests (110 unit + 39 BDD), all green on macOS ARM/Intel, Linux, Windows
• 36 official packages on pkg.wynlang.com
• 42 sample apps
• 49KB hello world binary (unchanged)
• 60+ doc pages, 16 blog posts, 0 orphaned pages

Full details: v1.11 release blog and what's new.

---

Next Quarter — v1.12+ (Q2–Q3 2026)

Developer Onboarding

New users bounce if they can't build something real in 15 minutes. We need to fix that.

Item	Owner	Effort	Details
Interactive "Learn Wyn in 30 Minutes" tutorial	content	L	Step-by-step in-browser tutorial. 8 lessons: variables → structs → concurrency. Each lesson has editable code + expected output.
Rewrite Getting Started page	content	S	Current page is too sparse. Add: "Build a CLI tool in 5 minutes" walkthrough with copy-paste commands.
"Your First Web Server" guide	content	M	End-to-end: install → write server → deploy. Include the 12-line zero-dep server.
Video: "Wyn in 10 Minutes"	content	M	Screen recording. Install, write fib, build, run. Post to YouTube, embed on homepage.
Cheat sheet PDF	design, content	S	One-page syntax reference. Print-friendly. Link from Getting Started and playground.

Community Building

A language without a community is a hobby project. We need to make it easy to contribute and talk to each other.

Item	Owner	Effort	Details
Discord server with #help, #showcase, #dev channels	community	S	Set up, write welcome message, pin getting-started links. Embed invite on site header.
CONTRIBUTING.md in every repo	community, content	S	How to file issues, PR conventions, code style, test requirements.
RFC process for language changes	engineering, content	M	Markdown-based RFCs in a rfcs/ repo. Template: motivation, design, alternatives, drawbacks. Required for any syntax change.
Monthly "State of Wyn" blog post	content	S	What shipped, what's next, community highlights. Keeps the project looking alive.
First-time contributor labels	community	S	Tag 10-15 issues as "good first issue" across wyn, site, and official-packages repos.

Documentation Gaps

60+ pages is a good start. But there are holes.

Item	Owner	Effort	Details
Complete stdlib API reference	content, engineering	L	Currently 24 stdlib pages. Missing: detailed function signatures, return types, error cases for every public function. Target: every function documented with at least one example.
10 new cookbook recipes	content	M	Recipes: HTTP client, JSON parsing, CSV processing, file watcher, CLI arg parsing, SQLite CRUD, regex extraction, env vars, logging setup, config files.
Error message catalog	content, engineering	M	Every Wyn compiler error with explanation and fix. Like Rust's error index.
"Wyn for X developers" — Rust, JavaScript editions	content	M	We have Python and Go migration guides. Add Rust (ownership comparison) and JavaScript (async comparison).
Video content: 4 screencasts per quarter	content	L	Topics: "Build a REST API," "Concurrency in Wyn," "Package Management," "Cross-Compilation."

Playground Improvements

The playground works but it's bare-bones. It should sell the language.

Item	Owner	Effort	Details
Share links (URL-encoded code)	engineering	M	Encode code in URL hash. "Share" button copies link. No backend storage needed.
12 curated examples (up from 4)	content	S	Add: concurrency, enums, pattern matching, error handling, generators, closures, structs with methods, string interpolation.
Mobile-friendly layout	design	M	Current textarea is unusable on phones. Responsive layout, larger touch targets, collapsible output panel.
Syntax highlighting in editor	engineering	M	Use CodeMirror or Monaco with our tmLanguage grammar. Currently a plain textarea.
"Tour of Wyn" mode	engineering, content	L	Guided walkthrough: 10 steps, each with explanation + editable code. Like Go's tour.

Package Ecosystem

36 official packages is a foundation. Community packages are what make an ecosystem.

Item	Owner	Effort	Details
Community package submission process	engineering, community	M	Form or PR-based submission to awesome-wyn. Basic review: builds, has tests, has README.
Package search on wynlang.com/packages	engineering	M	Current packages page is a static list. Add: search, filter by category, sort by downloads.
Package quality badges	engineering	S	Auto-generated: has tests ✓, has docs ✓, CI passing ✓. Displayed on package page.
5 new official packages	engineering	L	Targets: yaml, toml, websocket, markdown, template-engine. Based on what sample apps need most.
Package starter template	content	S	wyn pkg init scaffolds: src/, tests/, README.md, .github/workflows/ci.yml.

Performance & Benchmarks

Our benchmarks page is good but static. Developers want to verify claims.

Item	Owner	Effort	Details
Reproducible benchmark suite	engineering	M	Script that runs all benchmarks and outputs a markdown table. Anyone can run it: make bench.
Add memory benchmarks	engineering	S	Peak RSS for: hello world, 1M string ops, web server under load, 10K concurrent spawns.
Benchmark history (per-release tracking)	engineering	M	Track numbers across releases. Catch regressions. Display as a simple table, not a fancy chart.
Comparison methodology page	content	S	Explain how benchmarks are run, what flags, what hardware. Link from benchmarks page.

Blog Content Calendar

Blog posts drive traffic. Here's what we should write.

Post	Owner	Effort	Target Date
"Why Wyn Compiles to C (and Why That's Good)"	content	M	May 2026
"Building a Chat Server in 50 Lines of Wyn"	content	M	May 2026
"Wyn vs Go: An Honest Comparison"	content	L	June 2026
"How We Got 49KB Binaries"	content, engineering	M	June 2026
"Wyn's Concurrency Model Explained"	content	M	July 2026
"From Python to Wyn: A Migration Story"	content	M	July 2026
"Package Ecosystem Update: What's New"	content	S	August 2026
"Wyn v1.12 Release"	content	M	August 2026

Site UX

The site works. It could work better.

Item	Owner	Effort	Details
Dark/light toggle	design, engineering	S	We have a custom dark theme. Add a toggle button in the nav. Persist preference in localStorage.
Improved search	engineering	M	VitePress uses MiniSearch. Tune: boost doc titles, add search suggestions, show section context in results.
Mobile navigation	design	M	Hamburger menu is functional but cramped. Improve: larger tap targets, section grouping, sticky header.
"Edit this page" links	engineering	S	Link to GitHub source for every doc page. Lowers the barrier to community fixes.
Page load performance audit	engineering	S	Measure LCP, CLS, FID. Target: all Core Web Vitals green. Current status unknown.
404 page with search	design	S	Current 404 is generic. Add search box and links to popular pages.

Comparison Pages

Developers search "Wyn vs Go" and "Wyn vs Python." We should own those pages.

Page	Owner	Effort	Details
Wyn vs Go	content	L	Side-by-side: syntax, concurrency model, binary size, compile time, ecosystem size. Honest — say where Go wins.
Wyn vs Python	content	M	Focus: performance (85x fib), binary distribution, type safety. Acknowledge Python's ecosystem advantage.
Wyn vs Rust	content	M	Focus: learning curve, compile time, memory model (ARC vs borrow checker). Acknowledge Rust's safety guarantees.
Wyn vs Zig	content	M	Focus: C interop approach, build system, standard library philosophy. Smaller audience but high-signal developers.

Each page gets its own URL (/docs/guides/vs-go, etc.) for SEO. Include real code comparisons, not just bullet points.

Integration Guides

People need to know how to ship Wyn apps.

Guide	Owner	Effort	Details
Docker guide	content	S	Multi-stage Dockerfile. Build stage with Wyn + clang, runtime stage with just the 49KB binary.
GitHub Actions CI	content	S	Workflow file: install Wyn, wyn test, wyn build --release, upload artifact.
Deploy to Fly.io	content	M	Full walkthrough: Dockerfile → fly.toml → fly deploy. Include the web server sample.
Deploy to AWS Lambda	content	M	Custom runtime approach. Wyn binary as bootstrap. Include API Gateway setup.
Cross-compilation guide	content	S	Expand existing page. Add: CI matrix for multi-platform builds, artifact naming conventions.

---

Long-Term Vision (6–12 Months)

These are bigger bets. Some depend on language changes that need RFCs.

Language Server & IDE Experience

Item	Owner	Effort	Details
Language server (LSP) — go-to-definition	engineering	L	Parse project, build symbol table, respond to LSP requests. Start with go-to-definition and hover.
Language server — autocomplete	engineering	L	Complete: variable names, function names, struct fields, method names. Requires type inference integration.
Language server — diagnostics	engineering	M	Run wyn check on save, report errors inline. Reuse existing checker output.
VS Code extension: syntax highlighting + LSP	engineering	M	We have vscode-wyn with basic highlighting. Wire up LSP client. Add: snippets, bracket matching, format-on-save.
Neovim plugin: LSP integration	engineering	S	nvim-wyn exists. Add LSP config for nvim-lspconfig.
JetBrains plugin (basic)	engineering	L	TextMate grammar for highlighting. LSP integration if JetBrains supports it by then.

Language Features (RFC Required)

Feature	Owner	Effort	Details
Traits / interfaces	engineering	L	The biggest missing feature. Needed for: generic collections, serialization, custom iterators. Requires RFC, community input, and careful design.
Spawn with closures	engineering	M	Currently blocked by calling convention mismatch. Fix: box closure environment, pass pointer to spawn wrapper.
WASM target	engineering	L	Strip POSIX dependencies behind #ifdef. Compile to C → Emscripten → WASM. Enables: playground runs client-side, edge deployment.
Recursive spawn (goroutine-style)	engineering	L	Current thread pool deadlocks on deep recursive spawn. Needs work-stealing scheduler or goroutine-style stack switching.

Enterprise & Production

Item	Owner	Effort	Details
Structured logging (JSON output)	engineering	S	Log.json("event", data) for production log aggregation.
Profiler integration	engineering	M	wyn build --profile emits instrumentation. Output compatible with Chrome's trace viewer or perf.
Package lockfile	engineering	M	wyn.lock for reproducible builds. Pin exact versions of all transitive dependencies.
Private package registry support	engineering	M	wyn pkg install --registry https://internal.company.com/pkg. Auth via token.
Security audit of runtime	engineering	L	Third-party review of: ARC implementation, string handling, network stack, spawn/thread safety.

Learning & Certification

Item	Owner	Effort	Details
"The Wyn Programming Language" book — online edition	content	L	25 chapters already written in book/. Publish as a searchable web version on wynlang.com/book.
Wyn Exercises (like Exercism track)	content, community	L	30 graded exercises: easy (10), medium (15), hard (5). Auto-graded via wyn test.
University curriculum kit	content	M	Slides, assignments, and grading rubrics for a 1-semester "Systems Programming with Wyn" course.

---

What We're Not Doing (And Why)

• Self-hosting the compiler — The compiler is 55K lines of C. Rewriting it in Wyn is a multi-year project that doesn't help users today. Deferred to v2.0+.
• Native backend (skip C) — Compiling to C is Wyn's superpower: portable, debuggable, fast. A native backend would take years and lose those benefits. Not planned.
• GUI framework — We have the gui package for basics. A full framework (like Qt or Electron) is out of scope. We'll support community efforts instead.
• Package manager rewrite — wyn pkg works. It's not fancy. We'll improve it incrementally, not rewrite it.

---

How to Influence This Roadmap

• File an issue on github.com/wynlang/wyn with the roadmap label
• Join the discussion on Discord (link coming soon)
• Write an RFC for language changes — see the RFC process (coming Q2 2026)
• Contribute — check the "good first issue" labels across all repos