I think they said you couldn't use 3D features from OtherOS, so homebrew wasn't very interesting. My bet is that Sony did a very good job indeed and it was necessary four years to break the PS3 even though it's not completely done yet (you can't run software written on your own Blu-ray).

We'll still get great java and other JVM based language libraries from Apache.

If you have specific technical issues with java portability, I'm all ears, otherwise, you're the one drinking some kool-aid.

Nope, there are tons of libraries that support almost everything needed to develop for these platforms, I personally don't have any major problems with compatibility.

Java! Write once run anywhere. With a different GUI for each platform obviously.

You're not talking about Assange, you're talking about the guy that leaked the data in the first place.

Time you enjoy wasting is not wasted time.

I think they should just sue everyone they think is pirating their game instead of sending a threat first. This way justice will decide what should be done and there will be no blackmailing.

Two-thirds of the total people who died were civilians. That's obviously uninteresting!

Now you get my point, they are not able to implement the standard properly because the standard is so complex. That's the root of the problem and that's why wifi is better.

Just look at all those profiles and protocols. If they wanted it to work, they would keep it simple so everyone could interoperate without issues. See my previous comment: http://mobile.slashdot.org/comments.pl?sid=1838654&cid=34020828

My android phone notifies me about phone calls and sms messages I get on my Windows 7 desktop over bluetooth just fine. Now try this on Ubuntu or Mac and see what happens, nothing. Same app, same protocol, even same implementation (bluez on android and ubuntu)! I wrote the desktop program (http://code.google.com/p/android-notifier/) and we have a lot of people complaining that it doesn't work, the bluetooth stack generates cryptic error messages that does not mean anything because the OS decided to use its underlying socket abstraction to do RFCOMM I/O, errors during I/O are silently ignored, that sort of thing. IBM never implemented support for bluetooth in J9 JVM for my palm zire 72, you know why? Bluetooth is just a mess, it didn't work correctly with Windows XP at the time and alternative implementations like SuperWaba wouldn't implement a bluetooth API, they would expose it as a socket abstraction. We are better off using wifi that is better standardized and focused (just TCP/IP I/O) instead of bluetooth and its profiles, modes of operation, etc.

Bluetooth just doesn't work. It's was never meant to work and is more complex than it should.

Fixed that for you.