Wednesday, September 23, 2009

The Insanity of Google Chrome Frame

So Google is fixing Internet Explorer for Microsoft. Great, fine. You know what really pisses me off however? Is that Google decided this was a priority when you have people like Ray Ryan at Google I/O 2009 telling people we don't have infinite resources to get GWT 2/UiBuilder out the door.

Or the same speech about various AppEngine features. Like, for example, how about a JPA implementation that is actually worth a damn in AppEngine? Like instead of giving us a big speech about de-normalizing data on AppEngine, how about you use the current JPA annotations to do it for us, you have enough information in those annotations to do it for us.

Or a browser on Android that is actually good, you know with multi-touch and pinching. And don't give me that crap about Apple patterns. Apple is at war with Google, Google is just too dumb to realize it yet. Also, people, don't call the Android browser Chrome Lite, it's not fast enough to be deserving of the name Chrome just because it's WebKit based. The architecture of these 2 browsers are very, very different.