Desmond File

Blog archive

Brendan Eich: Browsers Sharpening JavaScript Performance

In the course of writing an upcoming cover feature on Google Chrome and its impact on Google's Web platform aspirations, I had a 30-minute talk with Brendan Eich. In addition to being the chief technical officer of Mozilla Corp., the commercial entity behind Firefox development, Eich also happens to be the creator of the JavaScript programming language.

JavaScript, of course, is central to AJAX-based development and to Google's Web strategy. Eich said that developers shouldn't be too quick to abandon JavaScript development for proprietary rich Internet application (RIA) frameworks like Silverlight and Adobe Flex.

"The thing against those platforms, which have their advantages for sure, is it just seems the Web is going to innovate over time and disrupt those single-vendor platforms," Eich said. "It may not have all the tooling at first or even eventually. It may not have all the platform coherence that a single vendor can make happen by throwing a lot of engineers and a team at the problem. But it will have the reach, provided the browsers are upgraded."

While the V8 JavaScript just-in-time compiler in Chrome has gotten plenty of coverage over the past few weeks, Eich and his team have been hard at work perfecting a JIT compiler of their own for Firefox. The TraceMonkey JavaScript engine is producing significant gains over the SpiderMonkey interpreter currently deployed in Firefox 3.1.

These projects, combined with a similar project for the Safari browser, mean that all the major browsers not named Internet Explorer currently have an aggressive JavaScript JIT rendering engine in play. The question is, will Microsoft follow suit with IE 8?

"I think they will," Eich said. "They have lots of people. They have JavaScript technology already in .NET and I think they can do it. I have colleagues at Microsoft on the Ecma [standards] committee and just the body language and casual conversation makes me think they will. I just don't know when."

Eich said Microsoft may be constrained by IE's longer update cycle and the need to preserve older versions of IE for existing corporate applications. But ultimately, he expects Microsoft will have no alternative but to arm developers and users with competitive JavaScript performance in IE 8.

The larger question, he said, is whether JavaScript will start to blunt the momentum of Flex and Silverlight.

"I would just be interested in hearing from your readers or whoever, if over time the Web is actually creeping in and disrupting those stacks. I think it is. Certainly it is the big consumer play," Eich said. "I don't see a lot of startups saying I am going to use Flash as my UI because I really need to go that extra distance with glitziness, or I really need Silverlight for that extra data-binding magic and language integrated query in C#."

What's your stance on the JavaScript versus Flex/Silverlight debate? E-mail me at mdesmond@reddevnews.com.

Posted by Michael Desmond on 09/23/2008


comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube