We're introducing the new https://t.co/t0PZL74vjg website built using the @Reactjs family of technologies.
Announced at F8 2019, this will be the web experience globally - itβs faster, easier to use, and gives your eyes a break w/ Dark Mode: https://t.co/WWGG6cOwk7
π§΅π
@joshuawx_ Some private schools are. Most of the public schools are out because of worries over busses and kids being stuck in the extreme cold *if* something happens. The snow chance is mostly just a catalyst. Plus if you're wrong, it has a much wider impact than a single school.
@Daniel_Bonds Kinda random I know but any chance you could have the graphics folks make those city names less prominent/blocking? Like the "ATLANTA" and its gray background blocks basically the entire city of Atlanta and you can't tell where the line between snow/sleet is at any given time.
@SafAriInTheCity@AFCEMA@AnthonyMKreis Our school won't bring hte kids in until this guidance is issued - in the meantime they're out there breathing this gunk
@StatisticsFTW@natebirdman I mean yeah it re-parents the components so they would remount. There's no way to get it to retain the current tree as a *suspense fallback*. BUT if you useTransition/startTransition, you can handle your loading state AND show the current tree while the transition is pending.
@joshuat Thanks, I ended up getting an invite from @kpk (thanks again!) but π bluesky account creation is currently disabled... Which basically underlines my point about failing to strike while the iron is hot!
You know I'd really love to switch over to bluesky but I'm still on the waitlist. Not that I'm all that important or anything but it feels like if they wanted to take advantage of the situation, you'd think twitter's competition would try to open up a bit faster?
@_developit I tried googling for this workaround and haven't seen any prior art but trying it myself in a classic worker seems to do the trick fine and let me still "do CPU work" while the script is fetching.
Parse/compile/exec still block but that's not nearly as bad as blocking on the IO.
Is there any way to reliably detect if you're running inside of a "type="module"" WebWorker vs a "classic" WebWorker?
The only way I can think of is calling importScripts and checking the error message, but that's not very robust...
cc @_developit maybe?
@_developit Random followup Q: You ever heard of anyone "polyfilling" async script import() on classic workers by doing:
fetch(scriptURL)
.then((res)=>res.text())
.then(s => importScripts( 'data:application/javascript;base64,' + btoa(s));
? Not ideal but maybe better than blocking.
@_developit Thanks for this. I think the missing piece I had was trying to use `data:,` as the test script - that lets it actually work on classic without any overhead. Thanks!!