Some Recent Videos About Websites That Are Pretty Good

Recently I have collected (and watched) some good videos, and it is difficult to decide whether to write a blog post separately or merge it into one. If there is more content to write for each video, I will introduce it separately, but this time I chose to merge it into one article to reduce the amount of text. Welcome to tell me your preferences for such articles in the comment section.

Tom Scott explains why the Internet is so chaotic

What happened to cookies? Part of the reason is. Humans are also one of the reasons.

This is the same Tom who made the awesome video with the title automatically updated based on the number of views.

An unknown author's accurate restoration of the Discord sidebar

Except ：hover acts on the number 8 itself rather than a link to a reasonable location, the other details are in place. However, this is more than the actual Discord<div> The usage of the mark is slightly better.<h3 id="Heydon-s-fancy-insights-on-progressive-enhancement"> Heydon's fancy insights on progressive enhancement</h3> <p> I can't embed the video here because even though Heydon seems to have switched to Vimeo instead of using it directly<code><video></video> Tags, privacy settings still lock it in briefs.video.

I like his point about "the basic layout is not a broken layout", but in this particular case it doesn't seem important to use @supports ? I like the @supports feature, especially after an awkward period when it no longer lacks browser support. However, I don't use it often because it's only really useful if you need to do something different than "make it not work", which I find is not common.

Houssein Djirdeh and Jason Miller discuss "Modern JavaScript"

We have to be very careful about the compiled code. One example is that a line of JavaScript code compiled into 7000 bytes, which is much larger and much slower than expected. Taking care of older browsers is a great thing when a large number of users use older browsers, but you might be surprised by the browser support for "modern JavaScript" and find that you compile more code than you need.

The key is that you can only really control the code you write, but most of the code you publish may be third-party code. This means npm, which absolutely contains a lot of very non-modern JavaScript code. They say the best option is to use ES 2017 as a general compilation target. If you need older browser support, you can use old differentiated service tips.

This video also has a blog version.

Jessica Chan Challenges William Candillon for CSSBattle

It is the literal CSSBattle website.

They tried back and forth how to make this little viral-like thing with spikes. I totally understand their approach! Neither of them are particularly smart in HTML or CSS – they are just trying to get it done. That's why I've never been involved in CSSBattle myself. I appreciate people’s skills ( of course ), but my actual CSS writing style is almost intentionally lengthy.