Mozilla, Microsoft reps argue over the future of web scripting
The process of creating ECMAScript 4—the next-generation JavaScript dialect—has become increasingly acrimonious as major stakeholders argue about the future of web scripting. The latest feud is between JavaScript creator Brendan Eich …
Context & Ripple Effects
The ECMAScript 4 fight is the most public split yet among browser vendors over who steers the evolution of web scripting, pitting JavaScript creator Brendan Eich and Mozilla against Microsoft's representatives inside the standards process. It lands during a bruising stretch for both camps: Microsoft is still operating under extended federal and state antitrust oversight following the October 30 announcement that a judge needs more time on policing terms, while Mozilla has spent the week fending off its own frictions — an analyst warning that Firefox faces a dangerous conflict of interest through its Google dependence, and a forced rename of Debian's Firefox build to IceWeasel.
That backdrop sharpens the stakes. For Mozilla, control of JavaScript's direction is one of the few levers of influence it holds independent of Google money; for Microsoft, resisting an ambitious new dialect fits its long posture of contesting externally imposed changes while under legal scrutiny.
First-order effects
- Mozilla's push for ECMAScript 4 now meets open Microsoft opposition inside the standardization process, leaving the next-generation JavaScript dialect's timeline and scope contested rather than settled.
- Brendan Eich's public feud raises the visibility of the split, forcing other stakeholders watching the process to pick sides or stay silent on record.
Second-order effects
- With the dialect itself in dispute, toolmakers and site developers building against tomorrow's JavaScript face uncertainty over which specification to target, pressuring the committee to either compromise or watch implementers diverge.
- Microsoft's obstruction posture lands while prosecutors and the DOJ weigh extended antitrust policing of the company, giving regulators another data point on how it engages with industry-standard processes.
Third-order effects
- If vendor conflict keeps overriding consensus, effective control of web language evolution drifts from standards committees toward whichever company ships the dominant implementation — making the browser, not the specification, the real arbiter of the platform.
- A stalled or forked ECMAScript 4 would entrench the status quo dialect, freezing web scripting capability at whatever each major browser already implements and raising the bar for any future overhaul.
The trend: Web standards are becoming a battleground where the pace and shape of the platform are set by shipping browser implementations rather than by committee agreement.