adambb

Unfortunate AI slop writeup for an otherwise interesting project.

As you delve further into the article, and (ironically, based on the topic) consider the ideas presented, it becomes more clear. Or skip to near the end to see.

TLDR: AI and generic pop culture artifacts have something in common - a lack of a certain type of depth that makes art great.

Agree with both points, at least for folks who already have that infra (which I do). Made it much simpler than trying to "extract" things out of a tool that wanted to do everything.

Liking this concept - definitely seems to have more design freedom and ability to iterate than say Claude Design and at a lower price (well it doesn't blow through it's entire "token budget" after 3 prompts anyhow!)

The "copy agent prompt" feature has what looks like a thorough prompt for the implementation, that can call back to DiffUI to grab assets and make SVGs and other things a FE dev would bug a designer for - nice touch!

To be fair to them, the architecture description said that each datasource had a unique agent, so the orchestrator AI didn't have direct data access, and that they specifically only allow access to data the user has permissions for.

Unclear if each datasource agent is ALSO AI based though, in which case it has just pushed the same concern down the line one hop.

(unintentional) satire? almost a meditation on the seemingly inevitable bloat of software

The great promise and the great disaster of LLMs is that for any topic on which we are "below average", the bland, average output seems to be a great improvement.

LG (UT8000 at least) TVs have an option to default to last used input, that works reliably.

I think the "messy ideas" was a reference to the homepage copy "Turn your messy ideas into crystal clear specs.", not continuing the previous thought about the placeholder. I'd agree that "messy" might have more negative connotations than you intended.

Learned a few things I didn't know about exception handling, like Vectored Exception Handling. If it's possible to somehow have enough permissions to install a generic vectored exception handler that has enough complexity to emulate generic instructions, not sure why the shellcode couldn't just be included there instead.

Maybe someone else will have a follow on regarding some product that does some more complicated processing in a VEH that could be used to implement something that has the same shape as this.