SMS Beats C# Benchmarks 1.26x Faster

Your phone's endless updates? They're bloating it with trackers you can't escape. SMS in Forge flips that: faster code, tiny APKs, no spying runtime.

Graph of SMS outperforming C# in speed benchmarks with hybrid compiler details

Key Takeaways

  • SMS hit 1.26x C# speed half-compiled; full AOT benchmarks next.
  • Hybrid interpreter/compiler enables secure remote scripts alongside native code.
  • APKs halved to 95MB; fights mobile bloat and surveillance.

Tired of Android updates that slow your phone to a crawl, stuffing it with ads and trackers you never asked for? Forge’s SMS compiler promises apps that run blazing fast, weigh half as much, and skip the surveillance entirely.

That’s the real win here. Not some lab benchmark. Developers building mobile tools — think indie game makers or solo app creators — get native speeds without C++ headaches or Kotlin boilerplate. And users? Lighter downloads, snappier performance, no Google overlord peeking at every tap.

Look, SMS clocked 1.26x faster than C# on March 24. Wild part? Event handlers and library calls were still interpreted. Half the compiler sat idle. Floor, not ceiling, they say.

What SMS Actually Delivers for Builders

No type declarations. Write var name = "Olaf". Compiler infers. Human-like flow, machine speed.

UI hooks? SML declares Button {id: myButton}, SMS reacts with on myButton.clicked() { doSomething() }. Ditch findViewById, XML hell, ViewModels.

Here’s the gem, straight from the source:

on button.clicked() log.success(“same code”) log.success(“interpreter or compiler”) log.success(“you decide at deploy time”)

Same code. Your call at deploy — interpret or compile. No rewrites.

Most languages? Pick a lane early: dynamic scripting or static grind. SMS laughs that off. Hybrid mode shines: trusted code compiles to AOT native (Android ARM now), remote scripts sandbox in interpreter. Lua in engines, browser JIT vibes — but FSS: Fucking Stupid Simple.

Why Does SMS Crush Traditional Benchmarks?

C# test? No GC hiccups. JVM? Warmup skipped. SMS events and libs? Interpreted. Yet faster.

Full compile flips it. Events compiled. Libs compiled. User logic compiled. Numbers pending — 5 warmups, 20 runs, median + p95, no cherry-picks. They’re eyeing C++ next. No malloc/free mess. Pure language horsepower.

APK shrinks: 188MB to 95MB. Ditched 32-bit. Half the weight.

But here’s my take — the unique angle they gloss over. This echoes JavaScript’s V8 revolution in 2008. Browsers were joke-slow; V8 ignited the web app boom. SMS could do that for mobile: force bloated runtimes (cough, ART) to slim down or die. Prediction? By 2026, half of indie Android apps ship hybrid-compiled, dragging Google into an open runtime war. ForgeOS — mobile-first, no Google, free hardware — accelerates it.

Skeptical? Fair. Benchmarks lie sometimes. But protocol’s tight, reproducible. And FSS? That 120-menu switch nightmare becomes 120 on menuX.clicked() lines. Zero dispatchers. Open in six months — obvious.

Is Forge’s ‘No Harm’ Compiler Easter Egg Genius or Gimmick?

Comment in compiler: // Do no harm to any living being. Used to be syntax rule. Now? Rewards good intent quietly. Cute nod — or PR fluff?

It’s smart psychology. Coders embedding ethics get subtle boosts. Amid AI ethics noise, this embeds virtue without preaching. But does it scale? We’ll see.

Pain point nails it. Phones track games, books, keystrokes. Updates invite worse devils. Forge fights back: less code, more security, no surveillance tax.

Market dynamics scream opportunity. Android devs hate bloat — 50%+ APKs over 100MB now. Kotlin/Java? Verbose. Flutter? Battery hog. SMS lands FSS native.

And remote scripts? Interpreter fallback by design. Secure hot-reloads, no full recompiles.

Why This Matters for Mobile Devs Right Now

Indies, you’re first adopters. Forge targets Android ARM AOT today. Build once, deploy interpreted or compiled.

Enterprise? Wait for C++ laps. But hybrid model’s killer for plugins, mods.

Bold call: SMS disrupts like Swift did iOS. Kotlin’s toast if APKs halve industry-wide.

ForgeOS vision — open stack, no gates — positions it as de-Google rebellion. Data: Android fragmentation kills 30% dev time. FSS fixes that.

Numbers will tell. Full benchmarks Saturday. But 1.26x partial? That’s signal.

**


🧬 Related Insights

Frequently Asked Questions**

What is SMS language in Forge?

SMS is a hybrid scripting/compiling language for Forge apps — no types, event-driven, FSS simple. Same code runs interpreted or AOT native.

How does SMS beat C# benchmarks?

1.26x faster March 24 with events/libs interpreted. Full compile (events, libs, logic) promises more. Transparent protocol ahead.

Will SMS replace Kotlin for Android apps?

Could — lighter APKs, simpler UI hooks, no boilerplate. But needs ecosystem. Watch ForgeOS push.

Elena Vasquez
Written by

Senior editor and generalist covering the biggest stories with a sharp, skeptical eye.

Frequently asked questions

What is SMS language in Forge?
SMS is a hybrid scripting/compiling language for Forge apps — no types, event-driven, FSS simple. Same code runs interpreted or AOT native.
How does SMS beat C# benchmarks?
1.26x faster March 24 with events/libs interpreted. Full compile (events, libs, logic) promises more. Transparent protocol ahead.
Will SMS replace Kotlin for Android apps?
Could — lighter APKs, simpler UI hooks, no boilerplate. But needs ecosystem. Watch ForgeOS push.

Worth sharing?

Get the best AI stories of the week in your inbox — no noise, no spam.

Originally reported by dev.to

Stay in the loop

The week's most important stories from theAIcatchup, delivered once a week.