What Oracle doesn’t like about Google

“We strongly recommend Java users consider alternatives to Chrome as soon as possible” those sound like fighting sounds and indeed Oracle doesn’t mince words if you try and install Java within Chrome. Mind you, Oracle didn’t throw the first punch, Google for “security” reasons is in the process of deprecating Netscape Plugin Application Programming Interface (NPAPI). Of course, NPAPI is from 1995 and a good funeral at sea is probably warranted at this stage. Nonetheless, this hasn’t left Oracle with any options for Java on Chrome.

While Google may not like Java, enterprises clearly do and there are thousands of legacy applications that are used daily by these companies, there are also thousands of programmers who know Java (Oracle says the number is 9 million but I’m only counting those still alive). These developers are quite happy to work with it and see continued employment in that field.  Legacy applications have long staying power as there is often little reason to re-work them if in fact, they’re still doing their job with the odd bit of TLC.

In short – Java ain’t going anywhere soon and this means users will need a browser that supports it, thus IT departments will lock down their users to a Microsoft browser, which means (ta da) that Enterprise WebRTC is going to be a Microsoft owned area for the moment. My university logic classes coming back to memory.

Oracle, on another side of their house, has been very supportive of WebRTC (they’ll be speaking at the forthcoming Kranky Geek Event) and in fact I’ve been impressed their enterprise communications offerings. Clearly they see browser based communications as being relevant.

Both Google and Microsoft are wooing developers to build solely on their platform. With both Oracle and Cisco tipping more towards Microsoft than Google, it will clearly be interesting to see how this plays out. I’d argue all to stop trying to pretend they’re cooperating (plus it’s a really slow process) and simply get their clan together and execute the best possible solution and let the best man win.

The risk of slow meandering is baffled users, no progress and the eventual introduction of an previously unknown 3rd party who simply shows up to steal the entire scene.

With all this mess, there is clearly room for a cloud based service provider to attempt to make life easier for all. The challenge will of course be in doing and doing it at a reasonable price. This is almost unavoidable as I don’t see the world of WebRTC compatibility coming together in the near or medium term.

An alternative is to simply ignore all of this, build for a single environment, try and force users to move to your chosen platform or simply give up that segment of the market. Doesn’t sound like a great investment pitch however, but probably the more reasonable one.