Slashdot Log In
MS, Mozilla Clashing Over JavaScript Update
Posted by
Zonk
on Friday November 02, @01:33PM
from the minor-frustration-of-the-titans dept.
from the minor-frustration-of-the-titans dept.
jfruhlinger writes "JavaScript has become a crucial part of Websites built on AJAX underpinnings, which makes the upcoming revision to the ECMAScript standard crucial for the future of the Web. But in today's browser environment, no one vendor can impose an update path — which may set things up for a nasty conflict. A fight is being fought on blogs between Mozilla Chief Technology Officer (and creator of JavaScript) Brendan Eich, who wants to the new ECMAScript standard to be a radical upgrade, and Chris Wilson, architect of MS's IE team, who would rather keep JavaScript as is and put new functionality into a brand-new language."
Related Stories
MS, Mozilla Clashing Over JavaScript Update
|
Log In/Create an Account
| Top
| 521 comments
(Spill at 50!) | Index Only
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Re:Why not both? (Score:5, Insightful)
Re:Why not both? (Score:5, Informative)
Go check it out and decide for yourself.
Ug. (Score:5, Insightful)
(Last Journal: Tuesday December 19 2006, @05:12PM)
Client side languages need to be concerned purely with the cosmetics of the interface. Any single step beyond that opens up some extremely scary security concerns.
Re:Ug. (Score:4, Insightful)
Re:Why not both? (Score:4, Insightful)
Re:Why not both? (Score:4, Insightful)
(http://www.pandora.com/people/apt142 | Last Journal: Friday March 16 2007, @02:15PM)
About Silverlight? (Score:5, Insightful)
(http://www.hyperborea.org/journal/ | Last Journal: Tuesday September 11, @05:30PM)
Re:About Silverlight? (Score:5, Funny)
function addOneWeek(startDate) {
var oneWeekInMilliseconds = 1000*60*60*24*7;
return new Date(startDate.getTime() + oneWeekInMilliseconds);
}
Re:About Silverlight? (Score:5, Insightful)
(http://www.gogo.co.nz/)
Re:About Silverlight? (Score:5, Informative)
(http://slashdot.org/ | Last Journal: Friday December 23 2005, @06:30PM)
And you are precisely echoing all of the lies that Brendan discredited in his post. There is absolutely nothing about ES4 that will break ES3. Nothing. Yet you (probably quite knowingly) propagate the falsehood that it will.
Re:About Silverlight? (Score:5, Insightful)
Because the story being discussed here isn't about Adobe lobbying a standards body in an effort to hold back adding new functionality to an open standard that could provide an alternative to closed add-on technologies like Silverlight and Flash.
If it was, people would be bashing them for trying to push the dominance of their proprietary solution by holding back standard, non-proprietary technology in the exact same way that Microsoft is being criticized here.
Microsoft wasn't criticized for having Silverlight, they were criticized for the manner in which they were perceived to be promoting Silverlight.
Yes, they are.
That's not what the dispute is over. The dispute is over whether Release 4 of ECMAScript should:
1) Include major new functionality, or
2) Include only minor new functionality, with major changes outside of the scope of the standard and left for other languages (either proprietary or part of different standards efforts.)
The first position favors substantial extensions to non-proprietary, freely-implementable standards for the web. The second does not.
A new version of a standard doesn't impose costs; no one is obligated to support the new version. ECMAScript Releases 1-3 won't stop working when a specification for ECMAScript Release 4 is released.
OTOH, more features in the standard means more that can be done within the scope of the standard and without non-standard, proprietary alternative technology.
New standards, even ones that aren't backward compatible, don't break old standards. ECMAScript 3 implementations don't break just because there is an ECMAScript 4 standard.
Re:About Silverlight? (Score:4, Insightful)
(http://www.earthcomber.com/)
Re:About Silverlight? (Score:5, Insightful)
(http://slashdot.org/ | Last Journal: Friday December 23 2005, @06:30PM)
Those are actually Brendan Eich's words. The extended commentary from which that comes is over here [mozilla.org].
MS do indeed want to close the internet, and the name of the game is "patent encumberance." It's going to be too hard to lock up JavaScript, so they don't want to play with that anymore. They need to have everyone investing in a new MS-proprietary, patent-encumbered language.
Re:About Silverlight? (Score:5, Insightful)
(http://www.zealot-trivia.net/ | Last Journal: Saturday July 24 2004, @11:46PM)
JS as a language is not fundamentally broken!
Multithreading! (Score:5, Interesting)
Re:Multithreading! (Score:4, Insightful)
(http://www.keiretsumusic.com/steve/ | Last Journal: Saturday February 17 2007, @05:51PM)
Disclosure: I am a web developer, but my use of javascript extends only as far as your "simple things like rollovers". (Well, not actually rollovers, that's done in CSS unless you're an idiot, but...) I am not a "proper" Developer. Hence, this genuine question:
To solve the problem of "the UI stalls the processing or the other way around" (which, funnily enough, I only ever really encounter right here on Slashdot), why would the script language need to provide multithreading to the script author (typical or otherwise).
Surely you could solve that particular issue by running Firefox-itself code in one thread, and on-page-javascript-or-whatever-script in another thread (or perhaps one thread per .js, or per site, or per tab, or whatever). You wouldn't need to actually let the script writer work in multiple threads, would you?
Re:Multithreading! (Score:5, Interesting)
(http://www.xenoveritas.org/ | Last Journal: Monday September 24, @04:04PM)
Yes, you would. The basic reason is that while, conceptually, you're right that you could use your solution to prevent the browser from locking up, you'd still have to worry about the page locking up.
JavaScript code is generally only executed during events. These events include relatively minor things like scrolling, clicking, typing, or basically any form of interaction with the page. Now you could make the page code "smart" and avoid locking the page if there are no JavaScript event handlers interested in the current event, but you'd still potentially have issues where the page would essentially "freeze" until whatever long-running task completed. Since JavaScript events also fire when the page is unloaded, such a "freeze" could also prevent the user from navigating away from the page.
This leaves us with a potentially responsive browser UI, but a tab that can't be used until its task completes. This is still better than the Firefox situation (and, due to the way Firefox is designed, something that isn't going to change in Firefox for a long while), but still undesirable.
To allow the page to remain responsive while the page is doing some long-running task, you'd have to allow multiple threads so that the event handlers could run.
This is, in a way, the problem that "asynchronous" part of AJAX solves. It doesn't allow another thread to be run via script, but it does allow the page to send the task back to the server to execute, allowing the page to remain responsive while whatever long-running task completes.
I think a similar solution could work via JavaScript: instead of sending it off to the server, allow a script to be executed asynchronously. It would have no access to any information not sent to it when it was started (as otherwise the thread synchronization issues would remain), but it could run a task and then return a result.
There can be some argument over whether JavaScript should ever be used for a "long-running task" but the reality is that more and more web applications are finding that it makes sense to allow certain tasks to run on the client instead of burdening the servers. Most clients have the memory and CPU to spare, and it makes sense to use those resources instead of making the bottle-neck be the server.
Unfortunately the current solutions cause the page to become non-responsive while JavaScript executes and, in the case of poorly designed browsers, cause the entire browser to be non-responsive.
Re:MOD PARENT TROLL (Score:4, Informative)
Yes, I have. There's a dating/forums site called plentyoffish that regularly freezes Firefox for me (at least as of 2.0.0.8). Sometimes the browser recovers quickly, sometimes it recovers slowly, sometimes I give up waiting and kill it.
To me, this seems vaguely pointless for browsers (Score:5, Insightful)
(http://www.wirewd.com/wh/)
The road forward, in true hacker fashion, is probably to write translators so that part of your PHP, Ruby, Perl, Java, or C# code magically runs on the client, treating ECMA 3 as a vague intermediate language.
ECMA 3 can be the x86 assembly language of teh intarweb. No CPU actually executes real x86 instructions anymore, they translate it into internal RISC/VLIW-ish operations. Very few programmers write much of any raw x86 instructions anymore.
Of course, this may or may not be handy for the other ECMAScript implementations like LiveScript.
Re:To me, this seems vaguely pointless for browser (Score:5, Insightful)
(http://www.latenightpc.com/blog/)
Personally I like Javascript as a language and think it's a shame to see roadblocks to it's development happen because of the nature of the platform it usually runs on. I'd like to see something like GWT where the source language is Javascript instead of Java - that is a Javascript to Javascript compiler where you could add whatever local features you need and have the compiler throw away the fluff and stick in cross-browser compatible shims.
Re:Opera is the Ron Paul of browsers (Score:4, Funny)
Just don't break things! (Score:4, Insightful)
(http://www.rru.com/~meo/)
Just don't break things that work now!
As a developer, I really don't care, either.
Just don't break things that work now!
Not sure about this... (Score:3, Insightful)
(http://ejksdesktop.homelinux.com/)
In short, give people a choice: Let me choose if I want to write for the stable venerable base or the new pretty whizbang version.
Re:Not sure about this... (Score:5, Insightful)
All current-day JavaScript will continue to work! Backward compatibility has been the number one goal during the development of ECMAScript 4. But Microsoft is scared - web applications have finally started fulfilling the original promise shown by Netscape, making the OS largely irrelevant. And so Microsoft is throwing up any- and all roadblocks it can think of, stalling for as much time as possible in order to create enough lock-in with WPF e.a. that they'll remain relevant. Understandable, of course - they're a company, trying to survive. But a really bad thing for the open web, and something which must be overcome.
Re:Not sure about this... (Score:4, Informative)
(http://leak.no-ip.org/)
[...]
Syntax
Some identifiers that were legal names in ES3 (let, yield, cast, is, and a few more) are keywords in ES4. Other keywords in ES4 were future reserved words in ES3, and correct ES3 programs do not use them (class, interface, public, private, and many others), though some implementations allow them to be used as names. Sometimes the new keywords are contextual and can continue to be used as names, but in general an ES4 implementation that must be able to process all ES3 programs must be told which dialect--ES3 or ES4--it is looking at, so that it knows whether to treat these identifiers as keywords or not.
The mechanism that supplies the dialect information will depend on the environment. In a web browser the information comes from the MIME type of the script or from a version parameter on the SCRIPT tag in the document. New web pages that choose to use ES4 will have to specify the dialect.
np: Savath & Savalas - Tormenta De La Flor (Golden Pollen)
What's this all about? (Score:5, Interesting)
I don't see anything about closing the web or stomping on the little guy or anything like that. Where's that coming from?
Re:What's this all about? (Score:4, Interesting)
The existing Javascript/ECMAScript has a large installed base. Thus if you simply extend the existing spec in a backwards-compatible way, you allow developers to
keep using Javascript and upgrade with new features at their convenience. This keeps everyone using Javascript and *should* be a smooth and gradual transition.
However, if you switch to a require a separate mechanism to execute or a incompatible language, you force developers to rewrite their code in order to take advantage of the new features. This may be philosophically cleaner, but doesn't have the continuity benefit of the other approach.
Now if you're Microsoft, which situation do you prefer? The second one, because it fragments the installed base and therefore the influence of the platform you don't control. That gives you an opportunity to sell people on using your technology platform instead, since they'll have to rewrite either way to use new advanced features. But if they don't have to rewrite completely, it makes more economic sense for developers to stick with Javascript.
Now there may very well be other technical arguments too, but the above is why people are suspicious of Microsoft's arguments. After all, Microsoft knows very well the power of an installed base and the benefits of having control over common technology platforms.
Wishes (Score:3, Funny)
(http://tarlus.homeip.net:12345/)
*sigh*
Re:Wishes (Score:5, Insightful)
Is there a non-elitist reason to not use tables for a layout?
There are many. Let's try a few:
Is that good for a starter? I'm about out of time to spend on this...
I don't think that browser support for tableless layout is perfect. It's awful in older browsers, but getting better all the time.
In any case, it's the browser's job to render the standard properly, not yours to break the code for the browser. I find the middle-ground is to k
brand new language (Score:3, Interesting)
Of course this is all just speculation. Wouldn't be the first time I'd be wrong, still, the smell is really strong.
Unfortunately, Microsoft has a point (Score:3, Insightful)
(http://www.animats.com)
The trouble is, Microsoft has a point. Original HTML, up to, say HTML 3.1, was limited but a reasonable design. Most of the attempts to extend past that point have been disappointing. CSS is a collection of attributes in search of an architecture. Page layout with "float" and "clear" is too limited and doesn't work well. (The "three column problem" is well known, and workarounds using layers or absolute positioning often result in text on top of other text.) Javascript is a mediocre language. (Could have been worse; see TCL.) That's the current mess.
Papering over the problem with a layer of "toolkits" just resulted in a proliferation of incompatible toolkit layers. That wasn't the solution.
But Microsoft will try to "fix" the problem with a closed, ambiguous system that requires frequent updates. That's what they do with everything else.
I don't see a good way out of this. Who can provide leadership? Adobe? They can't even make Dreamweaver work right any more.
Re: Unfortunately, Microsoft has a point (Score:4, Interesting)
(http://www.dolda2000.com/~fredrik/)
We already have a hypertext web that works very well with XHTML and CSS (not that they don't have their flaws, as you rightly point out, but they certainly work). What people are looking for with AJAX and Silverlight and what not is ways of delivering programs over the Internet in a secure manner, and Java already has that problem solved with both applets and Java Web Start. Java is also both an open specification and open source and it has a number of interpreters for almost any platform you can beg for, it has been around for far over a decade, and is very mature by now.
I don't see why people are not using Java. What's the problem? There are the obvious problems with Java being a horrible language to work in, but even so, it's probably still better than AJAX, Silverlight and Flash.