Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • Ah this is for embedded apps. Pretty neat!
    by sublinear
  • the amount of ai used in this makes me think its pure vaporware. has anyone actually confirmed any of this is real or works?
    by slopinthebag
  • It'll be cool to see how this compares with similar projects, there's a few of these jumping on the scene now.
    by ChocolateGod
  • > iOS Native mobile apps and device companion experiences

    > Android Gea apps packaged as a native Android APK, rendered through a WebView

    Why webview? No love for android?

    by potato-peeler
  • I'll keep an eye on this, it seems cool - write once in typescript, compiler compiles typescript into native apps. Seems like it combines ideas from React Native (one language/application model across platforms), Svelte (compiles away high level abstractions to avoid a heavy runtime), and Flutter (own enough of the UI model to target very different platforms).

    What I still don't understand (and can't find documentation for) is how Gea defines the portable abstraction boundary.

    The targets are radically different: embedded devices, native UI kits, framebuffer-style rendering, and webviews. The docs don't make it clear which Typescript/JS/node/browser semantics are guaranteed. If I write something like `requestAnimationFrame` and `fetch` and `queueMicrotask`, does it work on every target? The lack of caveats in the documentation implies "Yes" but provides no assurance. Where is the compatibility matrix?

    Does an application developer mostly stay inside a portable Gea model, or do they need to understand both Gea internals and the target platform to know what will work? If it's the latter, then it's hard to see the advantage of Gea vs just writing a native app.

    My impression right now is: potentially VERY interesting, but needs clearer technical documentation about the portability/limitations and convincing real world proof before I can believe it and let myself be excited about it :)

    Looking at the compiler repo, it looks like there is just one contributor. So I'm curious, what AI coding tools did you use? Which models? What's your workflow like? (I'm really interested in first hand experience on how models perform on truly difficult projects, not just at drawing pelicans)

    by desmondl
  • So essentially React Native but with the code not left in TypeScript/JavaScript but transpiled to C++?
    by mpweiher
  • 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.
    by jeswin
  • 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.
    by bertili

Explore Birbla archives