Linked by Thom Holwerda on Sat 21st Mar 2009 22:41 UTC
Thread beginning with comment 354410
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: javascript wars/to Thom
by Delgarde on Sun 22nd Mar 2009 20:29
in reply to "javascript wars/to Thom"
Thom, I know it's probably just journalistic freedom or something, but the javascript-wars were already going on between Gecko (Mozilla/Firefox) and Webkit (Safari at the time). For example Safari already had just before that releases a new and improved javascript-engine and Mozilla-guys were already busy with TraceMonkey. This is also the reason they could actually compete with Google's Javascript-engine.
Agreed - Chrome is nice, but it certainly didn't play any part in starting a new browser war - Gecko, WebKit, and Opera were already going at it enthusiastically long before Google jumped in. Google is just the most recent entrant in a competition that's been going on for a few years now... a competition I think largely inspired by the Acid2 and Acid3 tests...
RE[2]: javascript wars/to Thom
by ector on Sun 22nd Mar 2009 22:08
in reply to "RE: javascript wars/to Thom"




Member since:
2007-09-22
Thom, I know it's probably just journalistic freedom or something, but the javascript-wars were already going on between Gecko (Mozilla/Firefox) and Webkit (Safari at the time). For example Safari already had just before that releases a new and improved javascript-engine and Mozilla-guys were already busy with TraceMonkey. This is also the reason they could actually compete with Google's Javascript-engine. IE on the other hand, was still 3 optimisation steps behind. Although there rendering isn't to bad, which they say they focusing on is more useful.