Harsh (but fair) assessment of the performance costs of doing everything on the client side.
This is the rarely-seen hour-long version of my Resilience talk. It’s the director’s cut, if you will, featuring an Arthur C. Clarke sub-plot that goes from the telegraph to the World Wide Web to the space elevator.
It’s designed to read as a progressive enhancement when you look at the HTML it’s addressing.
Ben makes the very good point that template literals allow you to do a lot of useful stuff that previously would’ve required a library:
Template Literals afford a lot of power with no library overhead. I will definitely continue to use them when complexity of handlebars or similar is overkill.
Chris made a similar observation a little while back. Throw in a little script like lit-html and now you’ve got DOM-diffing too. You might not need insert-current-framework-name after all.
Kinda cool that these mini-libraries exist that do useful things for us, so when situations arise that we want a feature that a big library has, but don’t want to use the whole big library, we got smaller options.
I still haven’t used React (I know, I know) but this looks like a nice explanation of React and Redux.
I’m on Team Dave.
I’m all in favour of HTTPS everywhere, but this kind of strong-arming just feels like blackmail to me.
All new CSS properties won’t work without HTTPS‽ Come on!
I thought Mozilla was better than this.
A step-by-step guide to implementing drag’n’drop, and image previews with the Filereader API. No libraries or frameworks were harmed in the making of this article.
Third-party scripts are probably the #1 cause of poor performance and bad UX on the web.
The philosophy behind these tools matches my own philosophy (which I think is one of the most important factors in choosing a tool that works for you, not against you).
Slides from a conference talk with a really clear explanation of how
await works with promises.
This is a “what if?” scenario, but it’s all too plausible.
For site owners, the (partial) solution is to have a strong Content Security Policy.
(In the wake of Spectre and Meltdown, this is now a perfectly legitimate action for security-conscious web users to take; I hope your site can support that.)
A nice overview of the Payment Request API, which is getting more and more browser support.
Ooh, this is clever! Scott shows how you can use
And the whole thing is available here for free under a Creative Commons licence!