As I view on Chrome and what it means,
I’m struck by two things:
The immediate hit on Firefox and the strategic blow to Microsoft :)
I’m calling this Browser Conflict. The inventor of the browser hints to some of the same things here.
The grand tech story is that Google in essence copied Firefox!
It’s browser conflict. The war declared on Microsoft. The idea is the little old Javascript.
On the epitome Javascript is Javascript, but Google’s assault move takes this
little (major) element of the web and uses it against Microsoft.
Why? Because Microsoft Internet Explorer is weak when it comes to Javascript.
Chrome is 40x faster then Internet Explorer.
Little Javascript is the check mate move on Microsoft. Microsoft COM
is actually very good but Internet Explorer treat Javascript as a separate
silo even in how they develop the broswer - it’s a separate coding team.
So this makes the hidden master pieces- especially against
the big turtle now known as Internet Explorer.
Because of the relationship between COM and Javascript,
Microsoft incurs a huge “overhead” penalty in managing pages and interactions
- In the geek developer world this is called “taking out the trash” or garbage collecting.
IE 8 doesn’t really solve this problem of overhead.
Google is taking a small but important element in Javascript and using to
throw down IE in performance. As an end user I see immediate benefits on
page loads especially if I use the web a lot - hello that’s what the browser is for.
Google has it right in this version.
With Chrome Firefox in the short term is impacted, but the real loser will be Internet Explorer.
Dean and his team better get busy and fast. I’m a big fan of Internet Explorer since it’s inception,
but it’s time for Internet Explorer to compete and put out a faster product.
Better Microsoft better counter the Browser Judo with a move of their own.
