It's not that many js frameworks imply the need for a standard library. It's that many js frameworks, all providing the same functionality that many people wan

It's not that many js frameworks imply the need for a standard library. It's that many js frameworks, all providing the same functionality that many people want imply the need for a standard library. You mention cross-browser compatibility, he mentions web widgets. I don't see how anyone could oppose standardizing OS stuff like threads and IO on the server. If there were a large standard library built into javascript, I fear it would just be more things for different browser makers (especially Microsoft) to implement with different quirks... It's a lot easier to release your own incompatible (possibly "extended") version of a standard than it is to break existing software. MS can't even phase out IE6, even though they and the companies stuck using it acknowledge that IE6 needs to die. If MS released a browser version that broke many previously-working pages, it would probably trigger antitrust action by the government.