alt Hacker NewsIs Claude really this bad, though?
E.g. "The problem that never went away was async. Every framework, including ours, treated it as a condition that happened to it."
Async treated as a condition?
And a condition happens?
And on grammar, the second it is ... the framework??
I rather suspect this is second-order output. Writings of a brain rotted by "AI".
Shame, because enough of the message gets through the fog to tell me the whole message would be worth receiving. I wish the project every success.
Replies
The article reads eerily like the Claude-authored drafts I did for some internal explanations of Relay’s design philosophy (it’s a GraphQL client I’ve been advocating for). I’m not one to make accusations of AI authorship, but it was a particularly striking impression with this one.
I had to rewrite the drafts very heavily in my own voice in order for people to enjoy reading them —- not that I’m a great writer, but I am human and people tend to appreciate that.
Like a cold. Sometimes people call an illness a condition. A condition that can happen to you.
We have frameworks essentially living in a completely synchronous world--like a 2D plane--and they can't tell that there is another dimension out there except for when something inserts itself into its view out of nowhere. The protocol that we arrive at to deal with async is convoluted, because it is a state that is basically inflicted on the framework. That's what we sought to remedy.