3 ms·
It's not necessary to have a single person in charge, but it helps to have a single entity that can push changes through. Mozilla added a lot of features that n
by inimino 10y ago
It's not necessary to have a single person in charge, but it helps to have a single entity that can push changes through. Mozilla added a lot of features that never went anywhere because IE lacked them. The W3C never standardized JavaScript, but eventually ECMA did. The stagnation was caused by competitive factors between browsers and standardization didn't change that.
- deleted 10y ago[deleted]
- BrendanEich 10y agoChronology: when I was at Netscape and still (apart from part-time help) the only person working on JS and the DOM and the rest of the browser embedding, we took JS to ECMA (now Ecma) in 1996. It was never brought to the W3C. The IE stagnation came later, after IE4 which was innovative (because Microsoft wanted to embrace/extend/extinguish Netscape and the Web). Almost everything we added to JS at Mozilla made its way into standards. Examples range from __proto__ to generators in ES6.
- inimino 10y agoThanks for the clarification!