Wow, the website excels at showcasing the framework!
What are compiled binaries like with this and Dart? I've been building a sort of similar framework and engine in Nim, mostly because I can get binaries under 200Kb. I looked into implementing the concept in other languages but don't recall much with Dart.
Also, how does this carry over to Flutter? Is this similar enough that minimal changes would be needed to move a TUI app into Flutter's graphical domain?
Binaries in Dart are definitely larger than 200kb, I just AOT compiled one of the examples and it was ~7.4MB (arm64 MacOS). Dart has a few different targets it can compile to, but it generally requires a couple of MBs, as it packages the whole runtime.
Yeah, my goal definitely is to have to as close to Flutter where it makes sense. You should mostly be able to copy it over 1:1, with a couple of caveats (GUI and a TUI app have a few differences here and there).
That's what it was! I really, really wanted to use Dart because I love Flutter (only ever used it through FlutterFlow and was duly impressed) but I couldn't get around the binary size, mainly because I'm supporting WASM as a backend so it needs tiny binaries.
How did you handle the WASM backend? That part was extremely impressive to me. But aren't the binaries practically too large for WASM?
In any case, really love what you're doing and will be following progress. Outstanding work!
I haven't actually tried WASM yet. The demo on the landing page is using Dart transpiled to JS (embedded in xterm.js). But Dart does also support compiling to WASM directly, I'll give it a try tomorrow and let you know about the stats!
Very interesting, I always believed we should have more declarative frameworks in other domains and not just UI. My experience shows me this gives LLMs a much smaller space to explore which leads to better results.
Yeah, I fully agree. UI has become a pretty obvious example for declerative programming, but it probably makes sense for so many other domains as well!
Wow, the website excels at showcasing the framework!
What are compiled binaries like with this and Dart? I've been building a sort of similar framework and engine in Nim, mostly because I can get binaries under 200Kb. I looked into implementing the concept in other languages but don't recall much with Dart.
Also, how does this carry over to Flutter? Is this similar enough that minimal changes would be needed to move a TUI app into Flutter's graphical domain?
Thanks!
Binaries in Dart are definitely larger than 200kb, I just AOT compiled one of the examples and it was ~7.4MB (arm64 MacOS). Dart has a few different targets it can compile to, but it generally requires a couple of MBs, as it packages the whole runtime.
Yeah, my goal definitely is to have to as close to Flutter where it makes sense. You should mostly be able to copy it over 1:1, with a couple of caveats (GUI and a TUI app have a few differences here and there).
That's what it was! I really, really wanted to use Dart because I love Flutter (only ever used it through FlutterFlow and was duly impressed) but I couldn't get around the binary size, mainly because I'm supporting WASM as a backend so it needs tiny binaries.
How did you handle the WASM backend? That part was extremely impressive to me. But aren't the binaries practically too large for WASM?
In any case, really love what you're doing and will be following progress. Outstanding work!
I haven't actually tried WASM yet. The demo on the landing page is using Dart transpiled to JS (embedded in xterm.js). But Dart does also support compiling to WASM directly, I'll give it a try tomorrow and let you know about the stats!
Very interesting, I always believed we should have more declarative frameworks in other domains and not just UI. My experience shows me this gives LLMs a much smaller space to explore which leads to better results.
Yeah, I fully agree. UI has become a pretty obvious example for declerative programming, but it probably makes sense for so many other domains as well!