Crash CORE is (Almost) Here: Crash BASIC Beyond the Browser

If you’ve been following Crash BASIC for a bit, you know the current TypeScript build has been doing its job: fast iteration, easy deployment, and a smooth on-ramp for trying things instantly in the browser.

But it’s also been a very intentional stepping stone.

Now we’re approaching the next phase: Crash CORE - a new engine layer that’s on track to replace the original TypeScript version of Crash BASIC and push the project into something bigger: a true multi-platform runtime.

Why replace the TypeScript version at all?

The browser is amazing… and also a box.

A TypeScript-first runtime is perfect for web delivery, but once you start thinking about real platform targets - desktop builds, portable runtimes, tighter performance constraints, richer graphics backends, native integration - the browser starts to feel less like a home and more like a "demo stage."

Crash CORE is the plan to move Crash BASIC from "runs great in a tab" to "runs where games run."

What Crash CORE unlocks

Crash CORE is being designed to make Crash BASIC more portable by default. The goal is simple:

• Run Crash BASIC projects outside the browser
• Target multiple platforms without rewriting the language
• Keep the Crash BASIC vibe while upgrading the foundation

That means Crash BASIC can evolve from "web-native" to "platform-native," opening the door for builds that feel more like actual shipped games and apps - not just prototypes living behind a URL.

It still works in the browser (but better)

One important detail: moving to Crash CORE doesn’t mean leaving the browser behind.

Crash CORE is being built so Crash BASIC can run natively on multiple platforms and still run in the browser when you want it to - but instead of relying on the original TypeScript runtime, the browser build will be powered by Rust + WebAssembly (WASM).

That gives you the best of both worlds:

• Browser mode: the same instant "open a tab and go" experience, now backed by a Rust-driven WASM runtime
• Native mode: the same Crash BASIC projects can run as standalone builds on platforms outside the browser

So the story isn’t "web vs. native." It’s one core runtime, deployed wherever you need it - including the web.

What stays the same

This isn’t about changing the soul of Crash BASIC. It’s about making sure the soul isn’t trapped in one environment.

You should still expect:

• The same playful, expressive Crash BASIC style
• The same creative workflow
• The same "make something fun fast" energy

Crash CORE is about replacing the foundation, not the identity.

What happens next

In the short term, you’ll still see the TypeScript version doing what it does best: powering rapid development and keeping things easy to test.

But as Crash CORE comes online, it becomes the new default path - expanding Crash BASIC into a system that can grow into real standalone builds, with more reach and fewer constraints.

Crash BASIC is getting ready to leave the browser.
And Crash CORE is the thing that makes that possible - everywhere, including the web via Rust-powered WebAssembly.

Stay tuned. The Continuum is about to get a lot bigger.