January 5th, 2010 | by akoelewijn | published in cloud, mobile, oss, web
Google used to be a search company making profit on adds. Today’s release of the Nexus One ‘superphone’ illustrates that Google is turning into the next Microsoft: a supplier of software platforms and applications. The Nexus One isn’t a phone, it’s a device to access the web. It’s just another Operating System to use applictions, [...]
November 19th, 2009 | by akoelewijn | published in open standards, oss
Lots of news on Chrome OS today, but nothing to suprising as far as i can tell. Chrome OS is basically just an operating system than boots straight into a (full screen) browser. All your apps will be web apps. Seems logical. Most of the time i just boot my computer to get online: read [...]
May 30th, 2009 | by akoelewijn | published in open standards, web
I’ve just been watching the google wave presentation. Pretty amazing application, it’ll probably scare the hell out of a number of communication software providers. But what’s even more amazing is that it’s almost entirely build using HTML 5. Just one feature needs the Google Gears plugin: drag and drop of desktop resources to the web-page. [...]
April 8th, 2009 | by akoelewijn | published in java
Google just announced that their AppEngine will support Java. The good new: AppEngine is going to use a fairly regular JVM, with some functionality disabled like sockets and file writing. It should support other languages that compile to bytecode, like Scala or JRuby. No mention of Groovy, but i hope that’ll work soon too. Update: [...]
April 6th, 2009 | by akoelewijn | published in open standards, soa
Just read Web 2.0 Expo: the end of the online search driven era?. The article argues that LinkedData, aka the Semantic Web, aka Web 3.0, might be a threat to Googles dominating position. I was actually thinking the opposite. To me, Web 2.0 and SOA seem a bigger issue for Google. Web 2.0 interfaces are [...]
February 4th, 2009 | by akoelewijn | published in software development
Paul Buchheit has another good example why you shouldn’t completely design new products in design documents in his post Communicating with code: From that day until launch, every new feature went live immediately, and most new ideas were implemented as soon as possible. This resulted in a lot of churn — we re-wrote the frontend [...]
January 31st, 2009 | by akoelewijn | published in other
I’ve written a couple of articles for some magazine’s. Not many, just a couple. But every time i’m writing an article, i wonder why i do it. It’s not that i don’t want my articles to appear in a dead-tree magazine, but I’ve noticed that many magazines don’t make their content freely available on the [...]
