Monday, 23 April 2007

I question Adobe's cross-platform commitment

Adobe CEO questions Microsoft Silverlight cross-platform commitment. Well I question Adobe's. The Mac plugin for Flash 9 has been a bit finicky at best (granted I don't use it regularly). The Linux plugin is only now stable. There is no "official" version of Flex Builder for Linux despite this being Eclipse and there being no technical obstacle to releasing one. Apollo was originally not listed to be released on Linux and now will be released (like Flash 9) some months after. Guys you're either in this cross-platform, open world with us -- or you're just another Microsoft wannabe who is only a few billion dollars and a monopoly short of being just as bad. (While we at Buni love all operating systems, we do acknowledge a clear preference for no lock-in, open standards, open source and openness in general).

Commander Adama, Battlestar Galactica

"Make your choice", but make it carefully.

Technorati Tags:

Posted by acoliver at 1:03 PM in Open Source
Responses (16)

Why nothing specified by the JCP is ever open or free

Steve Loughran writes:

Contractual disputes between Apache and Sun notwithstanding, if you do get access to a JCP TCK, and the TCK is only available under NDA, then only a restricted subset of developers can see the tests. Those who have an access, have to keep it a secret. Although they can see the tests, they can't file bugreps that disclose public details of the test. That is, they could enter a bugrep that says "test 1032" failing, but not "test 1032 fails because https.proxyHost isnt set before java.net.URL ctor is called", or worse include a code snippet.

This is why at JBoss I never got involved in the compliance effort. At one point I really wanted to help as I knew we were under the gun, but I was unwilling to bind myself to Sun in this way. I feel that anything specified by a not truly open specification or design (despite any best intentions), is never truly open source. If Sun is serious about making the JDK or JavaEE open source, they actually should start with the CTK (they now call it Compatibility Test Kit as apposed to TCK). At the moment they dubiously determine the RIs (which are dubbed "correct") and even where those are open the CTK is not. From what I hear (not solely from my former coworkers) the CTKs are piles of poo as far as code goes (oops I hope that detail wasn't a trade secret).

Technorati Tags:

Posted by acoliver at 9:12 AM in Open Source
Responses (0)
« April »
SunMonTueWedThuFriSat
1234567
891011121314
15161718192021
22232425262728
2930