Linked by Thom Holwerda on Fri 18th Dec 2009 16:58 UTC
Permalink for comment 400392
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
More News »
Sponsored Links



Member since:
2005-07-06
I've got nothing fundamentally against the concept of Silverlight or even Flash, my issue is the development of these technologies, compatibility and patents. Both Adobe and Microsoft need to develop a way where third parties can create compatible implementations in the same way in which Java is developed by a committee, a test suite created and certified implementations are able to use the Silverlight branding to ensure compatibility between the various implementations.
Right now, however, Adobe has flat out refused to fully open up flash specifications which make implementing a compatible version all the more difficult. On the other hand Microsoft has Silverlight well documented (due to it being a recent project and having to conform to the new internal standards) but the downside is the issue of patents and transparency with the development process.
Again, I'm not fundamentally against the concept of Flash and Silverlight, the problem I have is the implementation side of it, when it goes off the drawing board and implemented by way of development processes, transparency between the main implementation and third parties.