RIP html5rocks! Definitely a highlight in my career. Proud of the entire team over the yrs. A global group of web devs producing some of the very best content EVER! It was such a joy to be part of it all since day 1, inspire so many, and see a community catalyze in the process.
Farewell to HTML5Rocks https://t.co/KuKAmUEKzp
I had so much fun with the team creating this, but priorities changed and it slowly languished. I'm glad we could keep the content and the links, well, linking.
@chrisota Def Getty/Getty Villa (two diff things), Huntington library (botanical gardens), Grand Central market DTLA, Original farmers market. So many good reccos.
LazyWeb: any way for a web app to feature detect that the "Allow Notifications" OS setting has been turned off? If the user previously gave access (Notification.permission === 'granted'), it would be useful signal to help educate users on how/where to re-enable.
Did web notifications get WAY less useful + engaging on Android 12? Seems the default now is to not show as a pop-up banner. Instead just a little icon in the status bar that's easy to miss :( Users are not going to find these settings. cc @ChromiumDev
@RichFelker@tomayac@steren@ChromiumDev Features we'd expect the majority of users to want (location for precise pickup, no typing) still end up having low acceptance rates. There's also the ever changing landscape of how each browser shows the permission UI + diffs btw desktop/mobile. Users constantly need to relearn.
@elado Found https://t.co/rUNwiqKvtZ which describes the problem.
Next's default setup for SplitChunksPlugin is https://t.co/pBjkUKDkBs, which splits libraries > 160KB into their own chunk. So everything is ending up there. Now to figure out how best to override!
Webpack/NextJS experts. I have a tree shakeable npm lib used across our app. Some large components only get used on a few pages. Next still bundles them with the lib bundle. Since most pages don't them, they hurt perf. What's the magic to keep them out, only load on needed pages?
@DanielKempner I think we're good on tree shaking. What's not working well is how Next creates bundles for shared libraries used across pages. Example of what I'm talking about: https://t.co/RR93kmUzwv
@bsmldrs If they get used _anywhere_ they end up in the same bundle. Thinking we need to mess with next's defaults for https://t.co/al4x4dyeRW.
Also don't want other teams needing to remember to write dynamic imports when consuming our core library :(
@bsmldrs Yep, we're dynamically loading the components on pages which consume the large bits from libA. My expectation was that Next/webpack wouldn't bundle those things with rest of libA.bundle.js, but instead, create a sep chunk. But that's not the case.