Slashdot Mirror


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?"

5 of 324 comments (clear)

  1. And... by TheP4st · · Score: 5, Insightful

    ...nothing of value were lost.

    --
    "I have downloaded hundreds and hundreds of records, why would I care if somebody downloads ours?" Robin Pecknold
  2. Re:Netflix by MrEricSir · · Score: 5, Insightful

    Yup. Would anyone have installed Silverlight if it hadn't been for Netflix?

    --
    There's no -1 for "I don't get it."
  3. Can you back up this claim? by Zontar_Thing_From_Ve · · Score: 5, Informative

    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.

    Really? Do tell how exactly those Silverlight protections have been circumvented. Unless you are talking about a streaming media recorder which simply records the stream as it plays on your PC, I am not aware of any way to defeat Silverlight DRM. The use of separate protected streams for audio and video is fiendishly clever and I've never heard of a successful way to crack it. A video forum where I regularly participate gets posts all the time asking how to record Netflix streams and nobody has ever suggested anything but a streaming media recorder.

  4. Re:Netflix by Guspaz · · Score: 5, Insightful

    Except Adobe is clearly moving towards killing off flash. They've announced the death of mobile flash in favour of HTML5, and it seems likely that desktop flash will eventually follow.

    After all, it doesn't really matter to Adobe what runtime is used. They don't make money off people downloading the Flash runtime. They do make money off selling the flash designer software, which costs hundreds of dollars, and the streaming server solutions. What difference does it make if Adobe's software is spitting out stuff that runs in the flash runtime or HTML5?

    My concern is that HTML5 is clearly not up to the level where it has feature parity (or stability/consistency) with Flash or Silverlight. For example, HTML5 currently has no agreed upon standard for dynamic audio. Sure, it can play a sound or music file, but if you want to actually generate or process audio, that's impossible. Mozilla and WebKit both have their own proprietary competing APIs to do this, but neither is final yet, and certainly not a standard.

    Given a few years, HTML5 will probably be able to replace Flash/Silverlight, but clearly not yet!

  5. Re:What about Video?? by randallman · · Score: 5, Informative

    Sorry. You're just wrong about the progressive download thing. And it's not in the scope of HTML5 to define bitrate or fragmented delivery. Fragmented delivery is turf for HTTP and bitrate is for the browser or embedded player.

    Read:

    14.35.2 Range Retrieval Requests

    HTTP retrieval requests using conditional or unconditional GET methods MAY request one or more sub-ranges of the entity, instead of the entire entity, using the Range request header, which applies to the entity returned as the result of the request:

                Range = "Range" ":" ranges-specifier

    Please read the HTTP 1.1 RFC

    http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html