this is the heart of Brendan's argument: Microsoft supports standards only to the point when they threaten proprietary alternatives. Then Microsoft stalls, delays and attempts to dumb down the advance - leaving the marketplace clear of any meaningful competition.
This link has been bookmarked by 8 people . It was first bookmarked on 20 Mar 2008, by Michael Wenzel.
-
27 Apr 09
-
Java/C#'ers use these to-JS compilers because they are too lazy/busy to bother with learning JS and I don't see that changing with ES4.
-
The last time I checked, they weren't exactly in the majority of ES3 userbase. I guess they are in the ES3 library writing segment but really building ES4 just to make their life easier
-
ES4 isn't a new version of ES3, its a completely different language that's been dunked in a tub of Javascript long enough to make it smell familiar
-
-
28 Jan 09
Gary Edwardsthe obvious conflict of interest between the standards-based web and proprietary platforms advanced by Microsoft, and the rationales for keeping the web's client-side programming language small while the proprietary platforms rapidly evolve support for large languages, does not help maintain the fiction that only clashing high-level philosophies are involved here.
Readers may not know that Ecma has no provision for "minor releases" of its standards, so any ES3.1 that was approved by TG1 would inevitably be given a whole edition number, presumably becoming the 4th Edition of ECMAScript. This is obviously contentious given all the years that the majority of TG1, sometimes even apparently including Microsoft representatives, has worked on ES4, and the developer expectations set by this long-standing effort.
A history of Microsoft's post-ES3 involvement in the ECMAScript standard group, leading up to the overt split in TG1 in March, is summarized here.
The history of ECMAScript since its beginnings in November 1996 shows that when Microsoft was behind in the market (against Netscape in 1996-1997), it moved aggressively in the standards body to evolve standards starting with ES1 through ES3. Once Microsoft dominated the market, the last edition of the standard was left to rot -- ES3 was finished in 1999 -- and even easy-to-fix standards conformance bugs in IE JScript went unfixed for eight years (so three years to go from Edition 1 to 3, then over eight to approach Edition 4). Now that the proposed 4th edition looks like a competitive threat, the world suddenly hears in detail about all those bugs, spun as differences afflicting "JavaScript" that should inform a new standard.-
Add Sticky NoteThe history of ECMAScript since its beginnings in November 1996 shows that when Microsoft was behind in the market (against Netscape in 1996-1997), it moved aggressively in the standards body to evolve standards starting with ES1 through ES3. Once Microsoft dominated the market, the last edition of the standard was left to rot -- ES3 was finished in 1999 -- and even easy-to-fix standards conformance bugs in IE JScript went unfixed for eight years (so three years to go from Edition 1 to 3, then over eight to approach Edition 4). Now that the proposed 4th edition looks like a competitive threat, the world suddenly hears in detail about all those bugs, spun as differences afflicting "JavaScript" that should inform a new standard.
-
-
Add Sticky Note
-
Correct on the diagnosis, wrong on the remedy! The Web is a document centric platform upon which we hope to build a universal platform of connectivity, communications and collaborative computing. Why can't the Web evolve to become a computational platform? MSOffice is the document centric layer of the Windows computational platform. Why can't the Web run applications that read/write and interact with documents that wrap the complexities of data, content, messaging and streaming multi media?
-
-
In my opinion the notion that we need to add features so that ajax programming would be easier is plain wrong. ajax is a hack and also the notion of a webapp is a hack. the web was created in a document centric view. All w3c standards are also based on the same document notion. The heart of the web, the HTTP protocol is designed to support a web of documents and as such is stateless.
the proper solution, IMO, is not to evolve ES for the benefit of ajax and webapps, but rather generalize the notion of a document browser that connects to a web of documents to a general purpose client engine that connects to a network of internet applications.
thus the current web (document) browser just becomes one such internet application.
-
-
20 Mar 08
-
05 Nov 07
-
01 Nov 07
Public Stiky Notes
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.