JavaScript

❗Article Status Notice: Inappropriate Tone/Word Usage

This article needs additional work to meet the wiki's Content Guidelines and be in line with our Mission Statement for comprehensive coverage of consumer protection issues. Specifically it uses wording throughout that is non-compliant with the Editorial guidelines of this wiki.

Learn more ▼

How You Can Help: If this is a non-Theme article (See: Article types):

• Persuasive language should not be used in the Wiki's voice. Avoid loaded words, or the causing of unnecessary offense, wherever possible.
• No direct attacks on named individuals or companies. Malice may be attributed to bad and proven offenders, but only through the use of quotation and citation - never in the Wiki's voice.

If this is a Theme article:

• Where argumentation is used make sure it is clear and direct but not inflammatory. Avoid strong language, or causing unnecessary offense.
• No direct attacks on named individuals or companies. Malice may be attributed to bad and proven offenders, in a formal and calm manner.

This notice will be removed once sufficient documentation has been added to establish the systemic nature of these issues. Once you believe the article is ready to have its notice removed, visit either the Moderator's noticeboard, or the Discord (join here) and post to the #appeals channel.

JavaScript (JS) is a programming language and core technology of the Web, alongside HTML and CSS. It was created by Brendan Eich in 1995. As of 2025, the overwhelming majority of websites (98.9%) uses JS for client-side webpage behavior. It's even used on the server-side (see Node.js).

JavaScript

Basic Information
Release Year	1995
Product Type	Software
In Production	Yes
Official Website	https://tc39.es/ecma262/multipage/

Consumer-impact summary

• Forced requirement: Many webpages (and even entire websites), force the user to keep JS enabled. In 2026, considering the advancements in HTML and CSS technology, there is no technical reason why any website (other than real-time simulations and low-latency gaming) would ever need JS. The only valid justification are legacy code-bases, since those are impractical to migrate to no-JS solutions. That is, newer web-sites have no reason to use JS, let alone mandate it.
• Excessive tracking: JS is much more capable than HTML and CSS combined to track user behavior, because of its first-class access to user-agent (UA) APIs. JS can communicate with almost any server (only limited by CORS) at any time (limited by connection availability), using a plethora of protocols. JS can get hardware information and compute a fingerprint of the device, user, or both.
• Targeted ads: JS makes it harder for ad-blockers to block ads, since it can be used to make overly-dynamic ads. The data collected by malicious JS makes it trivial to serve personalized ads, even across unrelated sites.
• Market control: JS (alongside Wasm) are built into almost every web-browser and UA, including "light-weight" ones (such as w3m). Incentivizing companies to use it for everything, since "there's no need to worry about compatibility or portability". Some people say that JS shouldn't even be a Web Standard, implying that it should be an extension or plug-in (such as Java Applets and Adobe Flash) the user willingly installs; this would reduce the incentive to use JS, as there's no guarantee the user has it.
• Security nightmare: JS is well-known for being a poorly-designed tool. This leads to programmers and even experienced software-devs to accidentally add vulnerabilities to their code. That, and the fact that JS is Turing-complete (both in practice and in theory) is a recipe for disaster, as it makes debugging and reverse-engineering impractical in many cases. The most common vulnerabilities found are:
  • XSS, which NoScript tries to mitigate
  • Arbitrary code execution and code injection. Typically caused by eval (part of the ECMAScript spec), but there are Web APIs (such as setTimeout and setInterval) that can be misused as well.
  • Remote code execution. This is used by hackers and crackers to build bot-nets for DDoS or crypto-mining, but it's mostly used for spyware since it can hide more easily.
  • Sandbox escape. Modern browsers compile JS to native CPU code (see JIT) to improve performance; this introduces a higher risk of sandbox-escape, as the code can more easily find vulnerabilities to manipulate the engine.

Incidents

Add one-paragraph summaries of incidents below in sub-sections, which link to each incident's main article while linking to the main article and including a short summary. It is acceptable to create an incident summary before the main page for an incident has been created. To link to the page use the "Hatnote" or "Main" templates.

If the company has numerous incidents then format them in a table (see Amazon for an example).

---

Add your text below this box. Once this section is complete, delete this box by clicking on it and pressing backspace.

This is a list of all consumer-protection incidents related to this product. Any incidents not mentioned here can be found in the JavaScript category.

Example incident one (date)

Short summary of the incident (could be the same as the summary preceding the article).

External links

• LibRedirect explaining why it exists, and how Google Chrome's MV3 limits it
• https://daringfireball.net/linked/2025/01/18/google-search-javascript
• https://blog.jim-nielsen.com/2025/javascript-required/
• https://techcrunch.com/2025/01/17/google-begins-requiring-javascript-for-google-search/
• https://serpapi.com/blog/google-now-requires-javascript/
• Google being anti-competitive towards Firefox: https://github.com/uBlockOrigin/uBlock-issues/discussions/3240
• Meta refusing to serve content to noscript users, and deliberately nagging them to install the app or login: https://github.com/Rudxain/uBO-rules/pull/9
• Websites that nag users to enable JS, even when it provides negligible value
• Discord being extremely bloated to the point of crashing when opening Developer-tools: https://github.com/Rudxain/uBO-rules/blob/42220bd4f80052ee15136dff7269df19529c43ec/rx.ubo#L3-L19
• "Enough with the JavaScript already!"
• "Maybe we could tone down the JavaScript"
• "You don't need JavaScript for that"
• "You really don't need all that JavaScript, I promise"
• "Progressive Enhancement Still Important"
• https://www.w3.org/wiki/The_principles_of_unobtrusive_JavaScript
• "Everyone has JS, right?"
• "Shipping a button in 2026…", by Kai Lentit. This illustrates the burnout and fatigue software developers can experience on a daily basis
• HTMX developer advocating for less JS
• "Web Obesity Crisis"
• "How web bloat impacts users with slow connections"
• JS bloat (2024)
• How JS makes web apps more unstable
• GNU/FSF explaining why JS takes freedom away
• GNU/FSF explaining why "web apps" shouldn't exist. WARNING: contains overzealous claims! (according to Rudxain). Related: Local-first
• Interactive page (game?) showing how websites can track almost anything the user does
• "Browserize" fingerprinting showcase
• "CreepJS" fingerprint showcase
• More sources (TO-DO)

See also

• Electron
• Mozilla