Chapter 2. JavaScript

Tell us what you think!

We’d love to hear your feedback on the JavaScript chapter of the 2020 Web Almanac. Leave a comment and tell us your questions, comments, and ideas.

How would you rate this chapter? (5 = best)
  • 1
  • 2
  • 3
  • 4
  • 5

0 voters

Chapter resources :nerd_face:

Here are some additional resources if you’d like to learn more about how this chapter was made:

Found a bug? :bug:

File an issue or submit a pull request on GitHub. Thanks for your help!

Join us! :seedling:

The Web Almanac was built with the support of over 100 contributors from the web community. If you’d like to contribute to the 2021 edition, please fill out our interest form and we’ll reach out to you in mid-2021.

Very simple explanation for the increase in usage of JavaScript in 2020: increase in required notices.

It is not surprising that we see this increase at all, considering the massive influx of required notices that would Masters are obligated to have presidents on variscite for legal reasons, whereas increase views hears these particular notices either did not exist or were not required. I’m referring of course to things such as cookie usage, gdpr, California privacy notification, adult content warning, etcetera.

The type of code that is used to power 99% of these particular types of notices? Guess what? JavaScript…

The only surprise in this is that the Gap isn’t larger. Just my humble opinion. Not really a revelation here in this article.

Just a small spelling issue found on the JS section. Image attached.

Thanks for pointing that out @chrislachance! We’ve got a fix queued up in a PR on GitHub. cc @tkadlec