« November 2008 | Main | January 2009 »

December 17, 2008

Google is inside an infinitive loop of political doublespeak

Google, the company powered by uranium, coal, oil, cheap Asian hardware, communism, lead, mercury, advertising, privacy invasions and copyright infringement is getting desperate. So desperate that they wrote their own anti-anti-ad technology platform known as Google Chrome. And then they wrote Android in such a way that the Java code can not be run on any Sun, IBM, HP, Apple or BEA/Oracle virtual machine. And finally they are now announcing Google Native Client, a project of epic desperation caused by the pathetic performance of AJAX and (based on how Flash performs on Vista) FLEX based applications.

Google is inside an infinitive loop of political doublespeak. Their party line is bullshit and the technology department is very well aware of this. So now Google is shoehorning the current Microsoft, Apple or Linux desktop API into a Google Mega-API to rule all other API's. Sort of like an #import “Google.hpp” for the Internet. And all you have to do is #define GOOGLE_LEAN_AND_MEAN in order to remove all that obsolete cruft from all those failed social networking applications. So instead of those stupid standards based wchar and char types you simply use gwchar and gchar in your C++ code.

I want to say something funny here, but Google is currently just depressing the hell out of me. Like... many OS X people will be running a Native Client x86 VM inside a Vmware x86 VM running on a processor pretending to be x86. Some server people will have four levels of code transformation because of hypervisors and Javascript support. Four ! And Java is bad because ?

I use Google services for many things, but why is forcing C++ into the web browser's security sandbox suddenly a sane decision ? Because Google people are “oh so clever” because of all those PHD's ? Well, Sun has a metric ton of people like that and the only thing that moves their stock ticker is, of all things, JavaFX. Yeah, yeah, not very scientific I know.

I think “Native Client” would be great on an operating system level. But on a web browser level this seems like folly. Firefox crashed twice this week because of Vista's DEP engine (probably a browser plug-in problem). I get the feeling that future Google code will give me “Guru Meditation” errors again. Google Chrome comes with separate processes for a reason.

The future of Google programming is “shit happens”. At least in Java you get a stack trace. Google is fixing a problem that has already been solved by Sun Microsystems, but they do not want to admit it.

This website is all about alpha and beta software

Download non-beta software here