Native apps written in TypeScript and CSS
arbayi
100 points
34 comments
September 22, 2026
Related Discussions
Found 5 related stories in 75.5ms across 7,406 title embeddings via pgvector HNSW
- Show HN: I built a native app for coding agents with Rust and GPUI 0x142857 · 22 pts · August 16, 2026 · 53% similar
- Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary maxloh · 90 pts · July 26, 2026 · 51% similar
- Old and new apps, via modern coding agents subset · 425 pts · July 12, 2026 · 49% similar
- Show HN: OTP Inspired actor supervisor based full stack templates annrap1d · 11 pts · July 20, 2026 · 49% similar
- Show HN: I built a zero-latency developer tool suite in pure Vanilla JavaScript AAPD_Studio · 19 pts · July 23, 2026 · 47% similar
Discussion Highlights (8 comments)
bertili
Not apparent at first, but this is a TypeScript to c++ compiler at the core ( https://github.com/geastack/compiler ), with bindings for various platforms.
sublinear
Ah this is for embedded apps. Pretty neat!
zerr
What do they use for graphics and audio?
tarcon
"The earlier implementation could not be driven to zero of them, because boxing was load-bearing in its emitter" In the docs of the repo of their TS to C++ compiler. https://github.com/geastack/compiler
slopinthebag
the amount of ai used in this makes me think its pure vaporware. has anyone actually confirmed any of this is real or works?
elendilm
Nice. I will keep an eye on this for future use.
realysy
How many memory does it cost for a simple hello world window? VS Qt, Tauri
jeswin
Author of tsonic.org here (which is very similar, but for Rust, C# and Mojo - WIP). One of the biggest complaints I get is about missing documentation on what TypeScript is not supported. For example, the following is obviously impossible: const a = eval("...something...."); or even: a: unknown, or a: any. The rest of it is largely doable. But people want to see what's not supported. Otherwise it's not clear to them what to avoid.