Right now it is just another marketing stunt.
3 years ago if I saw a post on the HN front page about a desktop environment written in Flutter (or a Swift port of Flutter), I'd be absolutely blown away.
Now, I see this, and I feel nothing. I'm not impressed. I don't want to know how it works. I'm not going to read 300k lines of AI slop code. I don't care about architectural decisions made because they're not made under any true constraints. I'm not even excited about the AI part of it, because I know AI can do this. We could all build this if we just prompt hard enough.
I'm tired, boss.
/edit Nevermind 'just' dart: https://github.com/starling-build/starling-engine#what-starl...
Still that part is kind of cool, 273K LOCs of the 335K
kstenerud•1h ago
A couple of things:
- The test pyramid (static -> unit -> functional -> VM release gate) works but is dependent on someone remembering to run it locally. Some kind of CI would help here.
- The C++ Swift interop layer has some huge files. Understandable given that you're porting the framework rather than reimplementing it, but right now it's the least documented, most god-object part of the codebase.