Wait until this guy finds out about htmx

This is what happens when a V also wants to do the M and the C.

But I would say most front-end libraries are insane: Their job is to manipulate a tree structure which is kinda slow (still?).

Who would have thought that this problem has such a crazy solution space!

From jQuery to Knockout.js to Angular to Vue to React to Svelte and many many others.

Only a couple of those understand that V = f(state) is only half the equation.

Coming from Angular, too, I never really liked React.

Angular had dependency injection and that made things so nice to work with.

React ended up with Redux and then contexts, which imo are both hacks in reaction to realising who in the fuck wants to pass down a singleton service component which maintains say a db connection down from the root of the project through all the damn layers of the app.

Define it at root, use in leaves via dependency injection. With Angular it was that simple.

Jsx/tsx was always hella cool though, I appreciate writing the v in the c, often with m. Angular from what I can recall was still very much mc, v.

I was like "gosh I feel like he's just complaining about the organic complexity in the domain" and then he says it at the end:

>So, this entire rant about React... it's not even React's fault. Neither is Angular's, or jQuery's. Simply, whichever tech you choose will inevitably crumble down under the impossible complexity of building a reactive UI.

and then he's like "ok the solution is to just not make big interactive software" and I'm like bro that is the opposite of a solution

separately, and I'm not sure how much this is really a nitpick: the bit where he complains about the two useEffects, that's indeed disgusting but that's because whoever wrote it is an idiot, that should be useMemo, and then it would be obvious to read etc. (well, maybe besides dependency arrays being at the end) -- more broadly I'm a bit like "I think you spent <10 hours using a framework, found it confusing, and got buttmad", which, whom among us, but also once again "bro if you just actually read the docs and spend time with it it's fine"

You can make a perfectly effective UI in vanilla HTML5 and it will work forever, just like you can roll up for your date wearing practical clothes driving a 2002 Honda Civic, but you’re not guaranteed to look impressive enough to snare the targets. I think the point of all this JavaScript library evolution is not to be a good coder or a practical husband.