Well, we have done it! Now we have created  and developed a new Javascript Engine called TraceMonkey.

Here is a few paragraphs below from LifeHacker.com about TraceMonkey:

How much do milliseconds really matter?

In short, plenty. JavaScript has become a predominant technology amongst today’s web developers, and Mozilla—along with pretty much every web browser maker out there—aims to make it just as fast as code that runs on your desktop. The closer everyone gets to that kind of speed, the closer the idea of the Web as Desktop gets to reality. This is handily demonstrated in a video demonstration of online photo editing over at Mozilla’s site. With just-in-time compiling, actions the user takes on a web program move along as if being adjusted in a desktop app, as opposed to having to basically re-load an entire JavaScript app and figure out what state it’s in. Oh, but you’re the numbers-and-graphs type, right? Mozilla has posted TraceMonkey benchmarks run on Apple’s SunSpider tester back in August. Here’s the basic overview graph:And here’s TraceMonkey pitted against Google Chrome’s much-touted V8 JavaScript engine, run by Mozilla on the same SunSpider benchmark suite: Now this is, as even Mozilla points out, just one test of JavaScript speed, and you’re only seeing what Firefox’s developers have publicly displayed. I tried running a TraceMonkey-enabled Firefox 3.1 build through the same Celtic Kane JavaScript test I used in our browser speed tests(one which at least one Firefox developer hasexpressed serious doubts about), but the results came back pretty noticeably off-key—timing out at 10 times slower than Chrome, or even Firefox 3.0. From human observation, I can say that Gmail did seem a good deal snappier using TraceMonkey, and Facebook’s mini-feed on my main page seemed to start folding down the page the instant the web page was called up. Of course, I’m using the highly-variable Windows Vista, and my Firefox 3.1 build was running no add-ons or external plug-ins. Still, it seems like Mozilla’s claims aren’t just inside-ball developer braggery—this monkey is a swift one.

So I should get ready to switch to Firefox 3.1?

We’re never shy about touting an open-source, highly-extendable browser, so feel free to try it out when it drops (or look below for help on giving it a test without disturbing your regular Firefox). But given how all the code for Firefox is available to anyone, Firefox’s SpiderMonkey engine is already being used in Yahoo Widgets, an offline Ultima Online server emulator, the JavaScript elements of the Windows-in-Linux WINE project, and likely a good number of other spots. If TraceMonkey’s speed makes a noticeable impact, you’ll likely see it put into place in those places and many more, and other browsers might just pick up on it as a mainstay or option, or at least develop their own versions.

Okay, I’m sold. How do I get TraceMonkey in my Firefox?

Our intrepid (and Firefox-loving) intern AsianAngelhas done the good work of detailing how to test out TraceMonkey without touching Firefox or any other browser you’ve got installed over at her blog. You’re basically installing a copy of Portable Firefox, then grabbing the latest beta build of Firefox 3.1 with TraceMonkey enabled and installing it into the guts of that Portable Firefox folder. Note that 3.1 comes with TraceMonkey enabled by default for web content, but you can also have TraceMonkey be the go-to handler for browser chrome (i.e. toolbars and display) and add-ons by enabling it in about:config

.

Your take

We’ve certainly said (and shown) our piece on TraceMonkey, but we’re just one team of bloggers, albeit a highly geeky one. We want to hear from our bleeding-edge fans how TraceMonkey is working in the wilds of the web, so tell us your take in the comments.

I think with Google Wave becoming such a platform for collaborative communication the possibilities are endless. If one developers wants to collaborate on documentation about a certain project with another developer he could do that either with in Google Wave itself or have Google Wave inside of Bespin.

We already know that developers can collaborate on code within Bespin using this Collaborative Feature similar to wave,but if you can write documentation or discuss issues about your code with other developers this would really make a developers job a lot easier.

We are getting into this new kind of real time collaboration on the internet and with combining these two great real time collaborative platforms together anything could be built.

I have joined Mozilla as a volunteer contributor to help them out on a new openn source project called Bespin.  Bespin is an online web development editor for web developers. I have been using Bespin with my own projects for over 7 months now and I love the fast perfomance of the HTML 5 Engine built into it and it’s sleak looking canvas style.

As the web gets faster web developers like myself need to start looking toward the future of web development and use new technologies like HTML 5,AJAX,Rails, and etc.  There is now doubt in my mind that within a few years from now all our desktop like systems will be accessed from the online using cloud based platforms.

The future of where we go on the web will be decided by these new technologies and these core systems. These tools will no doubt help us to build better web apps for the future of the internet.

The internet is just getting going and lets let code be shared for the world to see. That’s what I believe in.

Well, Bespin has been developing a lot of time into building and making Bespin Embedded work,but the plugin system they have for it is good,but what if you want to add more files to a plugin’s structure. Well, it seems that in order to do that you would need to end to build one file in your plugin directory called package.js and have JSON Objects in their as well as jaavscript.

As many of you know I have been developing my own feature for Bespin and it will be either a plugin or a tool just put into the main product,bespin editor on the Mozilla.com site. Although the plugin would be able to reach many more developers than the main product living on Bespin.Moizlla.com,but this idea I have for a feature for Bespin may not be as beneficial to the main site Bespin.Mozilla.com.  It might be a better fit for it to be a plugin for Bespin Embedded. I hope the plugins for Bespin are intended for the Bespin Embedded Editor and not the main product of Bespin.

So this idea I have will be a little bit like the Bespin File Manager,but be more of a shared code hosting like feature.

The folks at Mozilla said this about the new Plugin Feature for Bespin that they have just released below:

Bespin is built around a small core with most additional functionality placed in plugins. The driving goals behind plugins are:

• Allow lazy loading of functionality
• Be very easy to use
• Make it possible to update the editor without page reloads

“The ability to load functionality lazily is very important, because we expect that Bespin will have a large number of features, only some of which any given person is likely to use at one time. The simplest example of this is syntax highlighters: maybe you write JavaScript most of the time, but someone else is developing Ruby code. If you only use JavaScript, that’s the only syntax highlighter that will get loaded into your browser. And there are many more examples possible.

The Basics

A plugin consists of metadata and everything else. When you log into Bespin, the metadata for all of your plugins is loaded. Everything else (JavaScript, CSS, images, etc.) is loaded as needed. At its simplest, a plugin is a single .js file that contains a special section for the metadata.”

There is no doubt it my mind that Bespin won’t scale and become the world’s biggest and badest Online Code Editor on the web. When we say Code In The Cloud we mean Code In The Cloud!

Well I have been using Bespin since March and I have loved working with it,but an idea came to me that made me think of a code repository in Bespin. Now Bespin calls it self code in the cloud and it really is just that. So I am in the development of a new feature for Bespin and an Open Source Software called JBucket, a code repo for Bespin. Now yes their are a lot of Code Repos out their,but their is not a code repo that’s entirely powered by javascript and AJAX. A lot of code repos use eiher Python or some other langauge to develop their repo software.  The web is going in a new direction away from say desktop applications and using desktop apps that are online that look like your desktop email client or world processing client.

Mercurial and Git are two big repositories for hosting code,but their is no repo entirely developed in javascript and ajax. So why would I develop a javascript code repo engin? Well, first of all is that their are not a lot of examples of code repos that can embed them selves into an excisting cloud based development enviroment like Bespin and others. I don’t know about you,but i’d rather have my code backed up and stored online then on my desktop.  We all know of all those javascript libraries that are out their,but what about jaavscript code repo engines? None what so ever and if you don’t believe me just google it and you’ll see that their were none that I found.

JBucket is designed for Bespin,but it can be used with other apps as well and within a few months JBucket will be avaliable to others for learning and sharing. Like I have said on the right had side of my blog I believe code should be shared,not private unless for a particular good reason maybe security. Other than that code should be shared and used as an example for other developers to use it and learn it.

JBucket is a plugin for Bespin and will be released within a few months.

Please note that I am still working on this idea.