AI prose is great at celebrating whatever you told it to celebrate, but it always misses the most important detail: why should I care?
Starling: The first real desktop written by AI
21–30 of 33 posts
Re: Starling: The first real desktop written by AI
#22Re: Starling: The first real desktop written by AI
#23This post makes me feel grief. I mean no offence to you OP, this looks like a beautiful desktop and I am sure there was a lot of time put into this. But just sharing my grief. 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 work…
There is another angle for this story. Without AI, people like me can just dream about an idea, but never or difficult to implement those ideas. Now it’s just possible: https://starling.build/why.html
Re: Starling: The first real desktop written by AI
#24Earlier quoted context omitted.
There is another angle for this story. Without AI, people like me can just dream about an idea, but never or difficult to implement those ideas. Now it’s just possible: https://starling.build/why.html
But that page is also obviously written by AI. How do I know it's actually meaningful and not retroactively justified from the agent already having been instructed to create the project?
Re: Starling: The first real desktop written by AI
#25Re: Starling: The first real desktop written by AI
#26This post makes me feel grief. I mean no offence to you OP, this looks like a beautiful desktop and I am sure there was a lot of time put into this. But just sharing my grief. 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 work…
Then there’s the HNers who love that, nevermind the rules or intellectual curiosity, because they hope to likewise foist slop upon others and their agents and subagents are churning away even as they post their chatGPT "cleaned" comments about how awesome these products are.
These products need to go through a lot more before they come to HN. It’s not even AI-generation that’s the problem. Show at least a modicum of care, or earn trust by telling us who you are and why you made this (no, I don’t mean putting that in a Claude prompt and posting the result).
Re: Starling: The first real desktop written by AI
#27Earlier quoted context omitted.
I know the feeling but only people in our community care about how the software sausage is made. The customer only cares about results and it's great that AI can deliver results quickly. What I'm still waiting to see is evidence of reliability, performance and UX cohesion in these vibe coded applications.
Except for gamers, they are even more virulently anti-AI than this community is.
Re: Starling: The first real desktop written by AI
#28This post makes me feel grief. I mean no offence to you OP, this looks like a beautiful desktop and I am sure there was a lot of time put into this. But just sharing my grief. 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 work…
I know the feeling but only people in our community care about how the software sausage is made. The customer only cares about results and it's great that AI can deliver results quickly. What I'm still waiting to see is evidence of reliability, performance and UX cohesion in these vibe coded applications.
Re: Starling: The first real desktop written by AI
#29Well, AI or not, it is interesting to see Swift and Flutter without Dart. But is SNI Tray there? I see something in the top-right corner of that panel, but I'm not sure what it is.
Re: Starling: The first real desktop written by AI
#30Nicely done! This is an example of how engineering discipline mixed with good agent guidance can avoid the slop. 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 re…