Hacker News new | ask | show | jobs
by crooked-v 1367 days ago
This post ultimately seems to spend a long time complaining about other people not putting in the effort to fix the problems of React... while the author doesn't offer any solutions or even ideas for solutions.

Also, the author makes repeated digs at React 18's concurrent mode work while at the same time complaining about the kind of stuff concurrent mode is supposed to fix (for example, React updates not happening fast enough to keep up with mouse dragging).

2 comments

As soon as I saw, "you should listen to your elders" being used as a reason to read this article, i knew it wouldn't be high quality
That's a pretty inexperienced take, out of context. People should absolutely learn from elders, even if they feel the elders are wrong. Which is pretty much, every young person who has ever existed. There are often nuggets of wisdom buried inside resistance to change.

I often wonder how much further along we'd be as a society if we didn't spend the first couple decades thinking we know everything. Myself included.

"Wisdom" of elders should stand on its own by being well reasoned.

If someone needs to say "listen to your elders" then they aren't able to articulate their argument well enough to stand without it.

(I've been programming much longer than the 32 years claimed by the article author. No one should listen to me because I'm old, except in the case where I'm talking about specific incidents I witnessed that younger people didn't.)

> except in the case where I'm talking about specific incidents I witnessed that younger people didn't

All in interpretation. I implicitly assume 'listen to your elders' is about experience, not age. Perhaps others read that differently.

I don't think anyone is arguing a young PHD should do what an old chimney sweep tells him just because he's older. Unless of course said advice applies to PHD somehow.

The problem is that it's what inexperienced elders say to force their opinion on you.
So unnecessary too. Having experience in the domain, like teaching react, lends more creditability than "trust me, I am old".
No, teaching react is the opposite. When one is invested in the hammer all they see is nails type of analogy at play here. I personally dont do UI stuff and don’t know who is responsible for what I notice as a utter mess in UI, across the board not only on the web.
Aren't the majority of the core team in their 20s? Doesn't seem like age has much to do about anything here.
> the kind of stuff concurrent mode is supposed to fix (for example, React updates not happening fast enough to keep up with mouse dragging).

How does concurrent mode help with mouse dragging? I went reading through the React docs on this and they only really talk about data fetching patterns. I'm not sure I understand how it would apply to mouse events.

Doesn’t it help with having only high priority ui updates on the main ui thread with everything else happening in the background? To get low latency ui updates that’s exactly what you want: move everything except the low latency work to different threads.