These are the same things that Colly, then CEO of Symbian, was saying to me two years ago, when I was the chief strategy officer for Borland trying to convince Symbian that they needed a development tools partner. Two years later, the world looks the same to me (and I guess to Colly) -- why doesn't Colly recognize that:
- High-speed, reliable bandwidth is necessary for handset service-based applications to work and we don't have that now and won't have it for 10 years;
- there will always be a set of applications, or at least pieces of applications, that need to be on the device, not the network, and they need to be high performance -- think Doom as an obvious example and extend from there;
- 80% of all Java developers use the language as a SERVER development environment, not a client development environment. There are numerous problems with the quality of Java as a client side development tool, starting with standards;
- and then there is the problem with the size of the development communities. There are something like 2 million Java developers in the world (that is, professional developers, paid full time to write code). 20% of them use Java for real client side applications -- so we'll be generous -- 500,000 developers. There are 5 million developers using Microsoft tools, and 80% of them use MS for client side applications. That's roughly 4 million developers.
Is Colly trying to help out Microsoft? Convincing the non-MS world to ignore the need for a native device-side application development environment is tantamount to handing the market for handheld computing devices to Redmond.