dumbmatter

...which says

> Warning you probably don’t want to use CGI for modern web development, see Why Not to Use CGI.

Tons of shitty "here's how to use hooks for X" articles on Medium make the mistake, so people learning hooks right at the beginning will not be completely immune.

Also that the fix is "instead of using this one kind ref, use another kind of ref and put it in state"... I don't know, like I said I'm not sure if there is a better solution, but it still feels kind of unintuitive and complicated.

Now that I'm thinking about it... what is the reason that DOM refs and other refs need to be handled by the same concept? Every time I make a DOM ref, I'm doing something with it in a hook like useEffect. Why make me jump through hoops to re-run the hook if the DOM ref changes?

(I recognize there are probably good answers to those questions, the React folks are great, I just don't know the answers! Is it just to avoid introducing one more "type of thing", and instead making refs and DOM refs the same "thing"?)

I've seen a ton of people make that mistake, though. I think it's because what you write is accurate - "refs are meant for values that don't need to trigger a rerender" - but most people think of refs (or at least refs of DOM elements, which for many people are the only refs they ever use) as just a way to access a DOM element. They expect it to just be a DOM element in a normal variable.

I'm not sure if there is a less confusing way of doing it, but it's damn confusing.

I don't think that can explain it, because IIRC that rule has only been around since Obamacare, but the US/world price disparity for prescription drugs has existed much longer than that.

At least it'd be no worse than we have now with voting my mail.

Alternative title: Why does software development suck so much in _______?

And, sadly, if we could detect Alzheimer's a decade early, it would go from a 0% survival rate to a 0% survival rate.

Early detection would still be valuable for other reasons, though.

That's not true, 23andme tests the APOE gene (and possibly some others too) which does indeed have a large affect on the risk of developing Alzheimer's.

Although having the good version of APOE doesn't mean you'll never get it, and having the bad version doesn't mean you're guaranteed to get it. The odds do shift quite a bit, though.

Firefox 52 may be around for a while - it's the last LTS before extensions were broken by Quantum, and it's also the last release that runs on XP and Vista.