News ·
The first public beta is alive.
Sandwich Hime v1.0.0-beta.1 moved from a deeply tested source preview into the ordinary Go module ecosystem, ready for classrooms, learning, prototypes, and honest evaluation.
What became real
The compiler and Apache-2.0 runtime received separate signed tags. The vanity module paths resolve through canonical public Gitea source, the Go checksum database records the immutable modules, and fresh direct and public-proxy installs work without a sibling checkout or private workspace bridge.
The runtime stayed intentionally small and declared no third-party Go module requirements. Generated applications kept ordinary source, ordinary builds, and ownership of their own HTTP server.
What the word “beta” protects
Beta 1 invited real use without pretending the final-v1 compatibility promise had already been earned. Native Windows and executed Linux verification covered the supported Go lines; native macOS remained provisional. Security evidence named both demonstrated controls and unfinished work.
That honesty is part of the feature. Stability is the destination, not a label we borrow early.
Why it mattered personally
I wanted my younger brother to be able to take this into his Code Ninjas class and show learners that a language tool can be playful, direct, and serious about safety at the same time. The first release was an invitation: use it, change it, or do not—we are genuinely glad you are here with us.
Then we took the next careful step.