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!"
what else you could expect - Figma was born out of founder’s need to find a proof of concept test case for real-time collaboration JavaScript engine they created. They stumbled on this idea. Back then everyone used Sketch and wanted better prototyping and interaction design, and Figma appeared with its real time collaboration as major point which you used once just to try and never again. For occasional demos and in large organisations maybe it is useful, but with your average design team size is one person it’s not a problem to solve first. And yet despite having this real time collaboration you still couldn’t collaboratively present your design. You have to shout all the time “and now, what screen you’re on, what do you see?, yes click on that button on the left”. It shows how to this day, the UX is not at the table at Figma. They focus on opening offices all over the world and courting big clients. Because need growth, IPO.
Figma was first to employ an army of customer support “yes men” with sole task to answer in support forums and defuse frustrations this way, thus allowing Figma instead of fixing embarrassing bugs for years, to divert development resources to products nobody asked for, to fuel that growth.
Figma has became a product for investors rather than designers. And doing that it poisoned the design community, normalised bad UX and business practices.
Deleted Comment
It might be because I'm in a small org, but it seemed like big time sink vs time saver.
And this was far from painless: the system was unavailable for a whole day, and all manual interventions on the system (like comments, corrections, etc.) that had been done between the restoration date and the incident, were irretrievably lost. -- There were not too many of those apparently, but still.
I'm consulting for a company that makes around €1 billion annual turnover. They don't make their own backups. They rely on disk copies made by the datacenter operator, which happen randomly, and which they don't test themselves.
Recently a user error caused the production database to be destroyed. The most recent "backup" was four days old. Then we had to replay all transactions that happened during those four days. It's insane.
But the most insane part was, nobody was shocked or terrified about the incident. "Business as usual" it seems.