self incorporation

If JavaScript was going to be changed, I’d propose the addition of inherent namespace management.

Writing JavaScript in Java’s Syntax is for the abilities of refactoring large scale of scripts easily and reusing some APIs from Java, for example Eclipse SWT API for new HTML widgets.
About refactoring JavaScript, I had a pain experience of managing a 200k+ *.js (Sure, nowadays, we abuse large JavaScript). I want to refactor those JavaScript into new structures, or rename function names, or change the inheritances, or other things. That time, I had to do the job by searching and replacing without robust JavaScript plugin. But meanwhile such refactoring was just a piece of cake for Java in Eclipse. These days, IDEs for JavaScript, such as JSEclipse or others, come up, but not as robust as Java tools in my opinions.
There are lots of mature APIs and implementing codes in Java which can be reused. This is another reason of writing JavaScript in Java‘s syntax. In my opinions, JavaScript is designed for script without lots of library APIs. But as things developing, more and more functions are on the way of being implemented by JavaScript. So API comes to the way. APIs need times to be verified and be implemented. Then, why not just reusing Java or Python or other language’s mature APIs and implementations? I think, the next JavaScript concepts, like “package”, “namespace” and others, do help we developing new APIs and libraries.

/js (@_@)

IDEs are already appearing for JavaScript and Ajax, e.g., IBM’s Eclipse-based stuff.

Translators help authors use the new language only, even though not all browsers immediately support it. But as I said at the talk, at least Firefox and (I am betting) Opera will support the new edition quickly. Translating JS2 to JS1 will result in larger downloaded code size, reduced performance, greater difficulty debugging, and just greater bother than shipping JS2 source straight to browsers. So as Firefox and other browsers support the new language, any developer using such a compiler will want to bypass it when serving content to Firefox, et al.

This will likely put pressure on all browsers to support the new version.

There’s not much to be done about old browsers in the field, but we have many examples (XUL apps, Firefox extensions, web apps that target Firefox only, say in a kiosk or an intranet, and of course the Firefox front end itself) that we know will benefit from JS2.

Josson: Java and JavaScript are quite different languages. Why would you want to write one in the other’s syntax?

/be

I’ll look at it at home on the Mac though, quite curious.

JavaScript 2 and the Future of the Web（The Ajax Experience 2006） http://ajaxian.com/downloads/presentations/eich-ajax-experience-2006/ #from ajaxian.com http://ajaxian.com/archives/brendan-eich-javascript-2-and-the-future-of-the-web…

Are there useful tools to speed migration?
* A JS2 to JS offline translator, for example
* Write your web app using JS2 exclusively
* Run the translator over all of your JS2 code
* Serve the translated files to old browsers

The project Java2Script, which I am working on, is providing a Java to JavaScript convertor. To develop web applications, it recommends the way of writing JavaScript in Java Syntax (Actually writing Java totally by IDE and then converting Java to JavaScript).
But some comments sound

“Don’t turn it into Java!”

These comments do bewilder me and make me think further.
From the above Brendan’s presentation, we can see a lot of syntax improvements, which are popular in Java, C++, Python or Ruby. Maybe we could call them syntax sugars. Sugars won’t be enough. Robust IDEs are needed to help writing or managing those scripts.
So I am thinking: Will JavaScript 2 be on a way of being another language if it is not adopted widely and quickly by Browsers and IDEs while JavaScript 1 keeps being popular? If such things happen, a maybe JS2 to JS converter will always be used. Then JavaScript 2 will be similar to other languages like Java, Python, as those languages also can be converted into JavaScript by convertors. Then a question: why wait 2~4 years or longer for JavaScript 2 syntax sugars? Why not having the syntax sugars of Python, Ruby, Java or C++ right now by convertors?

PS: It seems that I am deeply affected by Java2Script to make such comments on JavaScript 2.

http://www.adobe.com/go/labs_flex2_downloads

It impliments the current draft spec, and will fully impliment the ECMA spec once it is finalized.

You can see the draft API docs for this at:

http://livedocs.macromedia.com/labs/1/flex20beta3/langref/index.html

(note, Flash and Flex specific APIs are mixed in with those docs).

mike chambers

Come on…am I the only one wishing this feature?

Ajaxian posted Brendan’s presentation at The Ahax Experience, called “JavaScript 2 and the Future of the Web”. Covers all the goodies JS2 will give us. One thing I noticed is the following point about class: – By default a class…