Or why browser monoculture is bound to become more and more of an issue. Sad to see Mozilla's weak response to this move. Can't bite the hand that feeds I guess.
Since the tooling is still far from great for web frontend memory analysis, it's nice to see some effort there.
Despite the problems with Mozilla's politics and funding, this is the main reason why I use Firefox as my main browser (even on my smartphone). We can't have a monopoly on which organization influence the web standards... unfortunately we get fairly close from that position.
Another frontend framework which seems lightweight. Especially nice is the fact that it's built on top of Web Components and that properties are properly reactive.
Since I'm still hoping for a strong RSS revival (not that it disappeared but I wish it was more the default option again), this post especially resonated with me. The discovery tool sounds very interesting.
Goes a bit in various directions but still interesting food for thought on the various way to strive for tech minimalism in what we produce.
Looks like a tiny and nonetheless powerful library for animations in web frontends.
Nice exploration of how to produce shadows in CSS. Make sure to read it all the way until the filter + drop-shadow approach.
Similar to RR but for web frontends.
Looks like an interesting web markdown editor.
A good reminder of what the Web really is. Yes, it's hard to add features to it, but look at the amazing backward compatibility! Everyone can write web pages and that's what matters.
Nice summary of the abilities coming from CSS transforms.
Interesting analysis on the impact of lazy-loading images in your pages. Bottom line is: don't do it blindly, it's actual better to not lazy-load some of the images.
There's been an announcement of MediaWiki adopting Vue.js. I think it's interesting to not stop at it and look what their workgroup evaluated and looked at to decide it was a good choice for them. There are a couple of interesting points in there.
Interesting guide on how to make the design of your frontend "eco friendly". Lots of tips in there on how to spare bandwidth and CPU time for the reader. Tends to push toward more minimalist designs which I definitely like. :-)
Ah! I thought this was often a missing piece in most React frontend code I've seen which mostly piles up useEffect and useState calls. Having a finite state machine is definitely a must have there, I'm glad some options actually exist, I didn't bump into XState so far I'll make sure to look into it.
At last some interesting tooling for profiling memory usage of web frontends. Clearly this is very early days though, this will get more interesting as the tooling makes progress. Some of the numbers in the benchmarks they came up with in this article are very scary though.
Where we're reminded that the stacking contexts with CSS is not tied to the DOM tree... Yay for making complicated rules which means you'll create such stacking contexts unexpectedly. This article comes with a couple of nice tricks to make things easier though like the isolation property. The CSS Stacking Context Inspector browser extension is good too.
In my question for simpler web frontends, this looks like an interesting library. It's built on Custom Elements (part of the Web Components effort) and is just a tiny bit of Javascript. Sounds neat and tidy.
I think this piece is getting quite a few points right. The SPA for everything trend rubs me the wrong way at least. As usual: use the right tool for the job.