Finally a haptic trackpad. Unfortunately not having one was a dealbreaker when purchasing my laptop last year, but next upgrade I'll be able to consider them again.

Yes, use the button element for buttons, and a for links.

But this is not a new problem or one "among the react crowd". Anecdotally I'd say it was more prevalent 10 or 15 years ago.

> But this is not a new problem or one "among the react crowd".

I'm really struggling to understand how the author connected using frameworks with using divs for clickable elements. And yes, this problem predated React and HTMX.

One of my biggest pet peeves is throwing shade at a certain tech or group of people who use that tech and the proceeding to demonstrate that they don't know anything about said tech.

the back button does work, if you use any basic routing library. opening in a new tab does work, with any basic routing library...

if you're receiving jarring page scrolling, it is not the fault of the spa, it's something else at play. it is not they typical spa experience.

if the back button doesn't work, the site was poorly programmed, since any routing library will handle that for you.

Bob himself has mentioned that many of the rules are contradictory to one another. I can't remember what examples he gave. I think it was in his video series.

Yeah, in the past month, I've caught out 2 bugs in a code review. One was a performance degradation due to a function being passed down into a react `useMemo` hook dependency array. The other was that the code was fixing a symptom, but not the cure.

I guess it depends on the quality of the reviewers.

Thank you! I couldn't originally figure this out for my "on air" script, so my workaround was to query the existance of the `zoom.us` process every second.

Interesting idea to remove number and string types. The downside being that you spend more time writing parsers of the data. But if you had some sort of separate schema that generated all of that for you, it would no longer be such a big deal.

They mention that their key/value pairs are ordered. The downside here is that not all languages (eg. javascript), support them.

I also prefer them to be unordered. The downside with ordered dictionaries, is that you need to always be asking "does sequence matter here?". So it adds an additional thing to think about, more tests need to be written, and certain optimisations can't always be made.

Both Objects and Maps in JS are in stable insertion order.

Apologies, it looks like pre es6, they were unordered objects. But now there are rules that guarantee insertion order.

I've never understood that position. Hooks and redux solve completely different problems. Why would the introduction of hooks change anything about using redux?

For JavaScript, https://javascriptweekly.com is pretty good.

I subscribe to several of their newsletters, and they're all good: https://cooperpress.com/publications/

Thanks for recommending us, folks. If it helps, they're mostly edited by HN readers too(!) (me in most, but not all, cases).