Or why upgrades need to happen with care, especially with an open platform like the web...
This looks like a very interesting dataviz framework.
Looks like a nifty little tool for sending notifications from a script to your phone or such.
Indeed, don't use this by default. This is likely overkill and has terrible side effects. Look up for the alternatives proposed in this article first.
Now this is indeed a very clever CSS trick!
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. :-)