Showing posts with label programming language. Show all posts
Showing posts with label programming language. Show all posts

Wednesday, October 8, 2008

JavaScript creator ponders past, future

Brendan Eich created JavaScript, the popular scripting linguistic communication being used to liven up Internet applications. Coupled with
XML, JavaScript have go portion of the Ajax (Asynchronous JavaScript and XML) technique popular in Web development. InfoWorld
recently met with Eich to speak about JavaScript: where it have been and where it is headed. Eich, who functions as main technology
military officer at Mozilla, also commented on other linguistic communications and about working with Microsoft in developing standards.

[ Take a circuit of today's Internet-oriented . ]

InfoWorld: As I understand it, JavaScript started out as Mocha, then became LiveScript and then became JavaScript when Netscape and
Sun got together. But it actually have nil to make with Java or not much to make with it, correct?

Eich: That’s right. It was all within six calendar months from May till December (1995) that it was Mocha and then LiveScript. And then
in early December, Netscape and Sun did a licence understanding and it became JavaScript. And the thought was to do it a complementary
scripting linguistic communication to travel with Java, with the compiled language.

InfoWorld: What’s the difference between ECMAScript and JavaScript, or are they one and the same?

Eich: ECMAScript is the criteria name for the language. Its figure is ECMA-262 and it’s A name that the criteria organic structure came up
with because they couldn’t acquire anybody to donate a hallmark that was congenial to all parties. So there’s Associate in Nursing issue with marketing
the scheduling languages.

JavaScript would have got been the ideal name because that’s what everyone called it and that’s what the books name it. Microsoft
couldn’t acquire a licence from Sun so they called their execution JScript. So ECMA wanted to name it something and they
couldn’t acquire anybody to donate or they couldn’t acquire everybody to hold to a contribution of the trademark, so they ended up inventing
ECMAScript, which sounds a small like a tegument disease. Cipher really desires it.

And so you have got got got this amusing [situation] where you have a criterion with a amusing name or figure and then assorted implementations
that have trade names. And the trade name calling don’t have got a immense value, except JavaScript is the common name. It’s inch all the
books, it’s what people say. It’s what people reference to on "Saturday Night Live."[Editor's note: JavaScript once merited mention during a skit on the show.]

InfoWorld: What was your chief end in developing JavaScript?

Eich: The thought was to do something that Web designers, people who may or may not have got much scheduling training, could utilize to
add a small spot of life or a small spot of smartings to their Web word forms and their Web pages.

So it’s 1995, the Web is very early. hypertext markup language was 3.2, I think, or something like that. People did not have got much programmability. Java was coming along at the same clip but it required you to utilize a high-powered programming linguistic communication and then run a compiler
and set your codification into a bundle that became an applet that was portion of the page but it was in a small silo. It was kind
of walled off. Alice Paul Krill is editor at big at InfoWorld. Continued1 | | | | | | »

Saturday, March 22, 2008

Google Launches Language Translation API - InformationWeek




Google for translating blocks of textual matter in Web pages into multiple languages.


The linguistic communication application scheduling interface can also place a peculiar linguistic communication before translation. The API do usage of the Web 2.0 engineering Ajax and covers 13 languages, including Arabic, Chinese, Dutch, English, French, German, Greek, Italian, Japanese, Korean, Portuguese, Russian, and Spanish. The API also back ups 29 interlingual rendition pairs.


The new API was developed by Google's Ajax Search and Feeds team, which on how the engineering can be incorporated in Web applications.


With the API, developers can interpret and observe blocks of textual matter in a blog or other Web page using Javascript, Google said. The linguistic communication tool is designed to supply interlingual rendition quickly when a more than thorough offline interlingual rendition is unavailable. Google bes after to add more than capablenesses to the new API in the future.


Google is offering a for usage of the API, as well as


Computerized interlingual rendition is an emerging tool in planetary business. In general, however, interlingual renditions be given to be either good when handled by world or fast when conducted by machines. The two rarely come up together in a single software system product.


One illustration of a software system company trying to better the procedure of getting concern stuffs translated is Parlance Technologies. The company last September introduced a new version of its WorldServer software system that includes unfastened APIs, so companies can incorporate Idiom's database for translated footing and phrases into other applications.


Google and security seller Symantec were among the Parlance clients that pushed Parlance to make the APIs.