Click here to receive your FREE subscription to Campus Technology
News
ECMAScript Fight Results in 'Harmony'
9/3/2008
The fate of ECMAScript 4 (ES4) appears to be sealed and, according to Brendan Eich, chief technical officer of Mozilla and the creator of JavaScript, so is the rift between the two factions of Ecma's Technical Committee 39, divided for a year over the future of this standard. Last month the committee officially agreed to ditch plans for the proposed ES 4.0 specification to focus on a more limited, new spec based on the current standard ECMAScript 3.1 (ES3.1).
Eich dubbed this larger, successor edition to ES3.1 "ES Harmony." That name, he said, was also meant "to describe the united committee and the agreements we reached." In his widely read blog post announcing the Ecma Committee's decision, he declared that the switch to Harmony was "good news for everyone."
"[The committee's decision] does mean that some of the ideas going back to the first ES4 proposals in 1999, implemented variously in JScript.NET and ActionScript, won't make it into any ES standard," Eich wrote. "But the benefit is collaboration on unified successor specifications to follow ES3, starting with ES3.1 and continuing after it with larger changes and improved specification techniques."
ES4 would have been a major fourth edition to the ECMA-262 specification. Proponents of this path advocated an ongoing evolution that would requires new syntax and possibly even new semantics. They sought to include things like stronger support for specifying the type of each variable, which is a more structured approach that's required by languages such as Java. They were also favored support for more sophisticated namespaces or packages that would prevent conflicts when two developers inadvertently use the same name for different methods. Advocates for the ES3.1, which is based on the existing ECMA-262 Edition 3 specification, pushed for a more model evolution.
The Ecma TC39 meeting held in Oslo at the end of July ended with a resolution to focus on four tasks, Eich reports:
- The shift to ES3.1, "with full collaboration of all parties," aiming for two interoperable implementations by early next year.
- Collaboration on the next step beyond ES3.1, "which will include syntactic extensions, but which will be more modest than ES4 in both semantic and syntactic innovation."
- The abandonment "for good" of several ES4 proposals, which the committee deemed "unsound for the Web," including: packages, namespaces and early binding.
- Rephrasing other goals and ideas from ES4 to keep consensus in the committee, including "a notion of classes based on existing ES3 concepts combined with proposed ES3.1 extensions."
JavaScript is one of the most popular dynamic scripting languages in use today, so the Ecma Committee's decision on the future of ECMAScript is going to affect a lot of developers. Eich advises those developers not to sit on the sidelines.
Recommended Reading
- Moodle Gets SCORM Improvements, Security Fixes
New versions of Moodle have been released, bringing the most recent stable build to 1.9.3. The latest round of updates includes a number of bug fixes and security enhancements, as well as improvements to the SCORM module.
- Free 'Morro' Antivirus To Replace Microsoft OneCare
Microsoft is rolling out a free antivirus software program for consumers that will compete with products made by Symantec and McAfee. Code-named "Morro," the AV app is expected to be available by the end of 2009.
- Microsoft Demos New SQL Server Features at PASS
Microsoft Wednesday previewed the ability to centrally manage applications and resources in the planned upgrade of SQL Server, code-named "Kilimanjaro."
- Microsoft Unveils Exchange and SharePoint as Services
Microsoft exec Stephen Elop on Monday announced two hosted solutions from Microsoft--Exchange Online and SharePoint Online--which are now available to organizations of all sizes in the United States. The software, paid for by annual subscriptions, is hosted on Microsoft's servers and supported by Microsoft's channel partners.
- 6 Ways Not To Become Rote Using Instructional Technology
There are, in my experience, six strategies to consider with any use of technology that will guard against rote use of technology and facilitate critical analysis of teaching and learning effectiveness. In this article, I'll share with you the checklist I work with and encourage others to work with in learning about and using new technology.
- Bringing Student Web "Stuff" to Campus Enterprise Systems
How can an institution incorporate Web 2.0 learning opportunities for students, and evidence of learning from those opportunities, into existing campus technologies and processes? PlugJam is providing part of the answer.
