Elliott Sprehn

As @RickByers mentions this is how the web has evolved for decades. I certainly don't agree with all API or system changes that have happened over the years, but stochastic progress is probably better than irrelevance. "Only on App Store" scares me a lot more than weird web apis

What's interesting about this narrative is that it narrowly focuses on JS. The whole web surface is the "standard" though, not just JS APIs. So for example Apple's ITP feature is also shipping a new web standard without other browsers being on board.https://twitter.com/Rich_Harris/status/1220412711768666114 …

I think type based overloading is probably a mistake. Instead it should be useState and useUpdater or something. This stumped a coworker for a whole week because the error message is about the state variable being of the wrong type (foo is not a property of undefined)

#React gotcha of the day! If your state is a function (ex. from a dynamic import), and you do [func, setFunc] = useState(), then import('...').then((f) => setFunc(f)) will fail because it invokes the updater form of setFunc which calls f() and sets the state to the return value.

I wish React would throw an exception by default if you assign to pushState or assign to window.location in a click handler and the target is not inside an <a href> with the same url.

LinkPrefetcher = ({ prefetch }) => <div onMouseEnterCapture={(e) => prefetch(http://e.target .closest('a'))}>{children}</div> And use the link href to know what to prefetch. Supports lazy (or never) hydrating, backend provided urls, links in 3p widgets, and more!

This is both cool, and demonstrates a pattern I see in React apps where folks add components on every leaf instead of using global listeners that are config driven (ex. with attrs). There's lots of power in that old school pattern though, even in React!https://twitter.com/ryanflorence/status/1206988974327128064 …

Super excited for this! Hopefully Chrome will add integrity hashes as an option here too.https://twitter.com/MylesBorins/status/1202797215296581633 …

Also the CEO of Away really needs a management coach. Seriously toxic stuff going on in the culture beyond even the slack rule obviously.

"totally transparent comms" === Junior people stressed out all the time.

Work folks need private spaces for discussions. Often folks say things and later realize they made a mistake, or that the escalation wasn't worth it, or that saying something more broadly would cause churn, etc. Only public comms turns all small issues into big public ones.

A great read about a dystopian and toxic company culture. It's also amazing that the "no email, only public slack" rule was done for inclusion, but created one of the most exclusionary cultures I've ever heard of. Don't buy from Away. https://www.theverge.com/platform/amp/2019/12/5/20995453/away-luggage-ceo-steph-korey-toxic-work-environment-travel-inclusion …

If she had instead joined the pentesting or fraud and abuse teams at a big tech company she probably could have been paid well for a job she's clearly qualified for! https://lite.cnn.io/en/article/h_e53ebe63a4743b3200980398eec1589a … (Also CNN lite is amazing, so fast!)

While very cool this is showing React yeilding the event loop to allow a main thread animation (raf powered) to have a better frame rate. Concurrent Mode doesn't make your 700ms renders magically take less time. This particular demo would also better as OffscreenCanvas.https://twitter.com/0xca0a/status/1199997552466288641 …

As a leader I've also observed it's often hard to tell power user issues (which employees tend to be) from issues that impact larger groups. It's good to practice empathy and take internal negative feedback as a signal to slowdown.