E3 this week: Sony Playstation 3 announcement eagerly awaited…

The E3 conference in LA starts this week (Tuesday May 16), and the most eagerly awaited announcement is surely going to be from Sony, and hopefully the unveiling of the new Playstation 3.

At this point no-one knows what exactly they are going to unveil, but it is expected they will have a working demo version of the Playstation 3.

Microsoft have already beaten Sony to it and annouced their new XBox 360 last week, with a media glitzy MTV TV special, but it seemed high on the glitz and low on any substantive information.

Lets hope Sony are able to give us a good look at the machine that we’ve been waiting for for the past couple of years since the hype started about their new ‘Cell’ processor.

Microsoft unveil XBox360 in TV show special

Microsoft unveiled the upcoming XBox 2, called the XBox 360, on a TV special on MTV yesterday.

I don’t think it is going to come close to the specs of the upcoming Playstation3 (which will also be demo’d at the E3 conference next week), but its interesting to note that Microsoft has departed from the cheap PC in a box approach, and is now also going to be using an IBM PowerPC based CPU with multiple processing cores.

Engadget has photos from the MTV launch show on their site.

Open Source Java – ‘Harmony’: do we really need it?

Apache have recently announced plans for an Open Source Java project, called ‘Harmony’.

I’m still in two minds about this. There has been a lot of pressure from the community for Sun to open source Java, but so far Sun have resisted. Instead they have implemented some other license agreements whereby they release and allow access to JVM source code early, during development and before the actual release, but as far as I know they are not soliciting community involvement.

I want to see the Java language and platform continue to grow, but right now it still is (not as fast as in the early days, such as in the first couple of years), and I’m not sure if community involvement would enhance the development and evolution of the platform or be harmful to it. For example, I see there could be a danger if anyone was allow to contribute the language would pick up so many different additions that would only be useful for some particular very specific problem (and < 5% of the time), that the language would end up overly bloated with unneeded features (as if it isn't heading that way anyway).

If you need additional features, whats wrong with producing a well documented open source API and release it as a Jar library that anyone can use, if they have a need for it. It doesn’t have to be included as part of the language, and people can choose whether they need it or not?