ongwt.com

Dion Almaer

 At a New Years Eve party, a friend help up a drink and toasted to his company deciding to discontinue direct support of IE 6 in 2009, and letting users know that the site may work better with IE 7 or another latest browser.

Removing IE6 from your supported browsers is the best way to cut costs.

onGWT.com hits 900 news !

I won’t support IE 6 in 2009

no comment

 

Dobes Vandermeer

I am the developer and user of online accounting software for small businesses written using the Google Web Toolkit (GWT).  When I tried our software in Chrome out of curiousity I was astounded to see how fast it was - first, it loads regular web pages as fast or faster than Opera, my old favorite browser.  Second, it loads and runs my accounting application much faster than I’ve ever seen before!

Google Chrome makes GWT apps Zoom !

 

no comment

Zviki Cohen

The main differentiator between JavaScript and other RIA technologies will be reduced to the visual complexity. Google are separating themselves from the herd by sticking with the clear and functional design approach. IMHO, it is a matter of personal preference. However, I will not be surprised to find future GWT releases providing more visual enhancements out of the box. GWT can walk hand in hand with Chrome and we might expect future releases of GWT to be "Chrome optimized".

I'm not sure it will be that easy to have a GWT permutation optimized for Chrome.

Google Chrome: "JavaScript Forever!"

2 comments

I have done a micro benchmark to compare Chrome/Firefox 3.0/Firefox TraceMonkey (3.1) and IE.

Algorithm	IE6	FF3	FF3.1	Chrome	Comments
Computation for(i=0 to 10millions) result+=i;	2800ms	945ms	40ms	200-2000ms	Strange : with Chrome results are not stable, each time the bench is restarted (not reloaded) the result is different
Building a table : for(i=0 to 1000) addALineOnTopOfATable();	1900ms	885ms	480ms	160ms	Chrome is faster
Moving an image : for(i=0 to 10000) moveTheImage();	1450ms	5308ms	912ms	450ms	Chrome is faster

 

Results are in milliseconds.

 

Test the Micro Benchmark

 

It was run on this machine (Windows XP SP2) :

5 comments

Ray :

The current browser wars make me feel like I'm watching the Fast and the Furious, and Google's new Chrome browser is like Nitrous Oxide for the web. As soon as I heard that ex-HotSpot guys were working on it, I knew it could be good, as they did a marvelous job with Self (a fully dynamic language), as well as Java, but how good?

Google Chrome smokes the competition on Chronoscope

no comment

Sundar Pichai

So why are we launching Google Chrome? Because we believe we can add value for users and, at the same time, help drive innovation on the web.

I think it is a very important news for the GWT community.

A fresh take on the browser

Comic

Google Chrome Screenshots

 

no comment

 

Philipp Lenssen

The browser will include a JavaScript Virtual Machine called V8, built from scratch by a team in Denmark, and open-sourced as well so other browsers could include it. One aim of V8 was to speed up JavaScript performance in the browser, as it’s such an important component on the web today. Google also say they’re using a “multi-process design” which they say means “a bit more memory up front” but over time also “less memory bloat.” When web pages or plug-ins do use a lot of memory, you can spot them in Chrome’s task manager, “placing blame where blame belongs.”

Google Chrome, Google’s Browser Project

 

1 comment

Firefox 3.0 is now in beta 4. I think it is time for us to test our application with this browser. I have just tested some GWT demonstrations with Firefox. All was perfect.

Firefox 3 beta 4 now available for download

Tested demonstration

Firefox 3 Memory Usage

3 comments