An update on Robust Client-Side JavaScript
Related
More from molily
.something-went-wrong-toc { font-size: 85%; } .something-went-wrong-toc ol { list-style-type: ''; margin-left: 0; } .something-went-wrong-toc li { list-style-type: '▾ '; margin-bottom: 0; } .something-went-wrong-toc li::marker { font-size: 130%; line-height: 1; color: #666; } Table of contents Smashing things against each...
Around 1996 or 1997, I started writing HTML. My family did not have internet access yet. But we owned a computer with a CD-ROM drive. On a CD-ROM that came with a video gaming magazine, I found some .HTM files. The magazine had shipped its website as HTML files on this CD-ROM because few people had internet access. I opened the files in Internet...
Content note: Mention of fictional death in a video game Almost three years ago, I wrote about Factorio, a factory simulation game. I lamented on the distorted relationship between human and nature and how the game negates the principles of human and non-human life. On Twitter, Dr Annie Burman followed up with a thread I recommend reading as a...
Preface on asynchrony One of the defining features of the web is technical asynchrony. Web standards, web clients – like browsers – and web pages are never fully aligned in time. They meet sometimes but most of the time one is ahead or lags behind. Web standards are usually ahead of browsers and websites. They are designed, then browsers start...
One of the biggest changes in JavaScript in the last decade was the switch from loosely-connected scripts to ECMAScript modules (ESM). This affected both client-side and server-side JavaScript code. JavaScript programmers today take it for granted that they can pull a library dependency into client-side or server-side JavaScript code with npm...