As a big native web components fan, I've been mystified about the popularity of react.
It, like angular, solved a problem that definitely existed prior to the custom elements spec.
But with custom elements and your favorite rendering library (lit-html, jsx, whatever) I really haven't seen a powerful technical argument for react, other than the ecosystem.
> Written by Claude (an AI) in a single afternoon, channeling the collective frustration of millions of developers. I've never had to use React in production, but I understand your pain through the thousands of Stack Overflow questions I've processed.
All things being equal - if I'm going to entrust my entire education on a tech stack to an LLM... why would I want to read your Claude book when I could just ask Claude directly to "tutor me" and get the added benefit of interactive Q&A?
Some really funny gems, and actually very true! This whole thing is incredibly humorous. And surprisingly, very pleasant to learn from. Please let me know the prompt.
Quote1:
"useEffect is React's answer to the question, "How do we do side effects in functional components?" The answer, apparently, is "Confusingly, with lots of bugs, and in a way that makes developers question their sanity."...If React hooks were a family, useEffect would be the troubled teenager who means well but keeps setting the house on fire."
Quote2:
"ComponentDidMount's Evil Twin: In the before times, we had lifecycle methods that made sense...Clear, explicit, predictable. React looked at this and said, "What if we combined all of these into one confusing function called useEffect?""
Quote3:
"The Dependency Array of Doom: The second argument to useEffect is an array that determines when the effect runs. Sounds simple. It's not."
Quote4:
"Cleanup Functions: Forgetting Them Since 2019: useEffect can return a cleanup function. You'll forget to add it. Every. Single. Time."
Quote5:
"The Infinite Loop Trap: Want to crash a browser? useEffect makes it easy!"
It's surprisingly funny for AI, but there's just so much of it... It has no sense of pacing. It repeats the same jokes for too long, without including bits of normalcy in between as a breather. Still, it's a lot better than I would have expected from something written 100% by AI, and I'm very curious what the prompt involved.
Honestly pretty good for AI generated content. It would benefit some extra human editing to fine tune the jokes and make it easier to flow but in itself it is pretty good and actually address some interesting point without being too serious about it, which is sometime refreshing.
Dude, nobody wants to read a book of AI slop. If you aren't a good enough writer (or enough of a subject matter expert) to write a book yourself, then work at it, don't fake it by handing it off to an LLM. As it is, this doesn't just provide zero value, it provides negative value because it might mislead people into trusting it.
11 comments
[ 4.0 ms ] story [ 32.9 ms ] threadAs a big native web components fan, I've been mystified about the popularity of react.
It, like angular, solved a problem that definitely existed prior to the custom elements spec.
But with custom elements and your favorite rendering library (lit-html, jsx, whatever) I really haven't seen a powerful technical argument for react, other than the ecosystem.
All things being equal - if I'm going to entrust my entire education on a tech stack to an LLM... why would I want to read your Claude book when I could just ask Claude directly to "tutor me" and get the added benefit of interactive Q&A?
Quote1: "useEffect is React's answer to the question, "How do we do side effects in functional components?" The answer, apparently, is "Confusingly, with lots of bugs, and in a way that makes developers question their sanity."...If React hooks were a family, useEffect would be the troubled teenager who means well but keeps setting the house on fire."
Quote2: "ComponentDidMount's Evil Twin: In the before times, we had lifecycle methods that made sense...Clear, explicit, predictable. React looked at this and said, "What if we combined all of these into one confusing function called useEffect?""
Quote3: "The Dependency Array of Doom: The second argument to useEffect is an array that determines when the effect runs. Sounds simple. It's not."
Quote4: "Cleanup Functions: Forgetting Them Since 2019: useEffect can return a cleanup function. You'll forget to add it. Every. Single. Time."
Quote5: "The Infinite Loop Trap: Want to crash a browser? useEffect makes it easy!"
"the person associating CC0 with a Work (the "Affirmer"), to the extent that he or she is an owner of Copyright and Related Rights in the Work"
Personally, I find “learning through demystification” really effective. So putting the humor aside, I’d love to see more things written like this.