In 1995, the web was a cobbled together community of hobbyists and enthusiasts. Some had years of experience in the computer science field. Others had none at all. So any language made specifically for the web, needed to be both powerful and approachable to the average developer.
In this modern era of web development, we don’t really need a heavy-handed reset, or even a reset at all, because CSS browser compatibility issues are much less likely than they were in the old IE 6 days.
Anyone who has even dabbled a little in creating websites knows that <div>s are an essential building block for controlling our layouts.
HTML5 introduced new semantic elements to help, and while they are a fantastic addition to the language, they’re a little bit like the garnish on our <div> soup.
The import() operator lets us dynamically load ECMAScript modules. But they can also be used to evaluate JavaScript code, as an alternative to eval(). This blog post explains how that works.
Can an event-stream incident happen again? How about other supply chain attacks? What will be the next vector of attack that we haven’t seen yet and might it be entirely preventable?