Microsoft Killing Silverlight?
SharkLaser writes "Silverlight 5 might be last version released by Microsoft. Several industry insiders and partners for the last few weeks have heard from their own Microsoft sources that there won't be new versions released after Silverlight 5. Status on service packs and support for Silverlight is unclear, as Microsoft haven't yet released lifecycle support end date even for the previous Silverlight 4. By their support page they will give full year head-up before ending support. With Adobe ending development of Flash for mobile browsers and Microsoft ending development of Silverlight, HTML5 video looks a lot more promising. But will content providers be able to give out their material without DRM and how does HTML5 perform with non-video side of Flash and Silverlight?"
...nothing of value were lost.
"I have downloaded hundreds and hundreds of records, why would I care if somebody downloads ours?" Robin Pecknold
Doesn't Netflix use Silverlight for streaming? Will Netflix move to some other technology?
Flash and Silverlight represent the mid-1990s way of doing things with third party browser addons. Back when we needed crutches like these, they were useful. The leg has healed, though, so it's time to throw the crutches under a bus.
Content producers should just suck up and use non-DRM video streams. They should all know by now that both Flash and Silverlight video "protections" have been circumvented just like Blu-Ray, DVD, etc and that there is really no technological recourse against this.
The idea that a general-purpose applet platform, with all the attendant security risks, is worth keeping simply to play DRM-encumbered video strikes me as utterly daft. It's like keeping a rabid rottweiler in your kid's playroom so that they'll have something to draw.
The streaming recorder works though, doesn't it? It's the "rubber hose" principle applied to Big Media - encrypt it all you want, but if you can see/hear it, you can copy it.
I thought DRM was already a thing of the past. Who is still doing that?
Just because it hasn't been cracked, it doesn't mean it's not crackable. At some point, the video must be decrypted and displayed to the user. Therefore, 100% bullet proof copy protection is impossible. The only way they can make DRM 100% full proof, is to encrypt it and throw away the key. At which point, you'll be watching random noise and listening to static.
I honestly can't see this as a big problem on Microsoft - they have quite a long track record of supporting their tools - even legacy Visual Basic skills can be used today quite effortlessly. Yes, they have had their misses and some tools or even languages (J++ comes to mind from the old days...) have been deprecated quite quickly after a blistering start but take a look around - there are frameworks and languages coming and going everywhere. If you want to bet safely learn C and C++ and code your own supporting libraries. Yes, it sucks when vendors pull plug on technology. But the days of learning Fortran or Visual Basic once and expecting to have guaranteed job for the rest of your life are over (well, if you are a true Fortran or VB genius you can get a nice paying job in maintenance these days...), And the same applies to OSS as well - they are not immune. Projects and languages come and go - yes, in the support side they are at an advantage because if you are a true guru you can dive into the source and support the platform - but I don't see the platform support as a huge issue on Microsoft side either. With right DLLs you can still run Win32 VB applications just fine - yes, the vendor doesn't support those anymore and doesn't develop new features but you still got what you have when you chose the platform.
Can you give examples of Open Source projects (in programming) which Microsoft has tried to emulate and has ended up with barely working and sucking copy?
Silverlight on web had really no big and bright future, it was just a poke on Adobe to steal marketshare on (DRM) video delivery. But those skills learned there are not totally wasted, it is not *that* hard to transform from one Microsoft architecture to another. But if your big bet was Silverlight on browsers (cross-platform/browser) then well, you are out of luck but it did not require a genius to figure that out from the start.