Post

Yeah some unsolicated hot takes in no particular order 1. React is better than everything that came before it and I haven't seen anything do it better 2. Hooks are genius 3. If you've never done frontend on a moderately large app, you probably underestimate frontend engineering

dan@danabra.mov

it’s always funny to me when people try to paint react as some kind of “big company” propaganda. it was like one person’s wild idea and then there was at most ~5 people maintaining it for years. people HATED it when fb open sourced it. the only reason it won is because the model was actually good

8 reposts258 likes

Yep ->

fry69@fry69.dev

That is also how I experienced it through the years. What are the alternatives if you take React out of the equation? Angular? Ember.js? Some Java monstrosity? PHP? Python/Django? Writing a complex website that stays maintainable is not trivial. React is on the low end of complexity IMHO.

The Elm language (originally based on functional reactive programming) was cleaner, terser, more elegant, and a better developer experience long before React, but being a new language means having a much smaller ecosystem.

I still very much prefer using vanilla HTML5/JS/CSS generally. It can do a lot — more than you’d think — and frankly a lot of stuff that uses React doesn’t need React However, like you said, the value of React becomes pretty obvious above a certain level of complexity

Angular has actually gotten really good in recent years - it’s opinionated and well suited for web apps, but it’s not a Swiss Army knife like React (because it’s not just a rendering library)

I am just going to take this from the vibe coder/tinkerer perspective ... having a complete UI/UX library that you can just basically pick and choose from, and it looks fabulous, makes developing quick basic one task apps so easy, and USABLE too. F em.

IIRC something about too many screens being kept in memory? I remember Samuel talking about it, I'm hoping that fix gets released soon

hmm, I was still experiencing that behavior yesterday then (while writing that reply, in fact) I still get noticeable lag (especially in the post composer) in some cases I'll test it out some more; any way I can help profile or diagnose those kinds of issues? I'm on Firefox

Thinking you could do better than the most widely used tool for a job is sort of like thinking you can walk into a casino and beat the house.

💯 Frontend development is mostly an asynchronous state problem. Hooks and modeling components as a simple transformation function from data to UI seems obvious now, but was revolutionary then.

If react is so good, why does literally no modern alternative (solid, svelte, etc) adopt the same model and prefers to use reactive primitives (ie signals) instead? Hooks seem pretty lame in comparison, with their rules.

because those frameworks are by and large horizontal moves that make specific (mostly questionable) tradeoffs with React rather than transcend it in any meaningful way

1. Agree with the first half. Some pretty slick things got invented later, maybe inspired by React to some degree. 1.1. I think React led to the large-scale renewed interest in functional programming. 2. Conceptually, yes. The way they work on top of JS is… a bit iffy. 3. Absolutely agree.

wow a hot take thats actually a hot take (because it's completely and utterly wrong), svelte at least (and probably solid/vue too) is soo much better than react

"I agree" says the 5k file with 100s of jsx components Jokes aside, from my experience, it's far easier to mess up jsx than the other two An then, I really enjoy {#if} and {#each} much more than .map and multiple ternary conditions, how can jsx be better?