Show HN: Frond – a frontend runtime for your app's dependency graph

A new project called Frond showed up with a bold pitch: stop managing your app with a messy pile of “if this is ready” checks, logout cleanup chores, and mystery background tasks, and instead make everything explicit and organized. In plain English, it wants developers to describe what parts of an app depend on what, so when a user logs out, all the right stuff shuts down automatically instead of relying on one poor soul to remember a giant checklist. That promise got attention fast.

But the real fireworks were in the comments. The biggest reaction was basically: cool idea, but why does it look like so much code? One commenter went straight for the jugular, asking why anyone would use this over simpler state tools that seem to do “mostly the same” thing with “10× less code.” Ouch. Another agreed the cleanup story is the interesting part, not the state itself, and wondered if Frond is really just sneaking a more advanced backend-style dependency system into the browser.

Then came the style police. One commenter looked at the towering wall of TypeScript and declared it practically begging for its own language, which is the kind of nerd insult that lands like a chair shot in this crowd. And because no launch thread is complete without a doom question, someone also asked about cyclic dependencies — aka, what happens when your carefully organized graph starts eating its own tail. No big memes here, but the vibe was clear: admiration mixed with suspicion, curiosity mixed with “please do not make me write all that.”