4 ms·

Maybe. But as a paying MLB.tv customer, the Silverlight implementation was TERRIBLE. Despite having all year to make improvements, the thing never worked even

by seekely 18y ago

Maybe. But as a paying MLB.tv customer, the Silverlight implementation was TERRIBLE. Despite having all year to make improvements, the thing never worked even remotely correctly. I scolded myself as I signed up this year, but there really aren't any other options. To my surprise, I started up the first game today (go Tribe), and couldn't believe how much the player improved. Judging by how many more (functioning) features and polish are in the Flash player than were in the Silverlight player, I suspect it wasn't just market penetration.

msie 18y ago
Adobe has more at stake in seeing Flash succeed than MS does in seeing Silverlight succeed. This may be reflected by the amount of Adobe support and development committed to the Flash platform. I'm sure the Silverlight team is way smaller.
- dantheman 18y ago
  True, but unfortunately adobe is stuck using AS3 on their VM; silverlight gets to leverage all the .net work. Hopefully they'll add threads to flash sometime in the future, that is the most limiting factor facing it today.
  - TJensen 18y ago
    I cringe to think what the developers at my work would do with threads in the Flash VM. I'd just as soon keep a single-threaded model.
    - dantheman 18y ago
      The single thread model has some serious limitations. For instance maybe you would like to load some images & then popup a component containing them. In a threaded world, you can have synchronous communication where it just waits till the download is complete before loading what depends on it. Right now you have to register callbacks, sure that's not too tough, but chaining like that makes it more difficult than it should be. download -> componentA > componentB > ComponentC whereas it might be easier to just go: CompnentA(file.download()); instead of file.Download (CompACallback, FaultCallback);
- neovive 18y ago
  This is a major point in favor of Flash. The adoption and expansion of Flash into the enterprise is critical to the future of Adobe. Thus, Adobe will continue to invest heavily on improving and expanding the Flash player, API, support and development tools. Microsoft could drop Silverlight with little impact on the company -- it's not critical to the success of Windows at this point.

by seekely 18y ago

msie 18y ago

Adobe has more at stake in seeing Flash succeed than MS does in seeing Silverlight succeed. This may be reflected by the amount of Adobe support and development committed to the Flash platform. I'm sure the Silverlight team is way smaller.

dantheman 18y ago
True, but unfortunately adobe is stuck using AS3 on their VM; silverlight gets to leverage all the .net work. Hopefully they'll add threads to flash sometime in the future, that is the most limiting factor facing it today.
- TJensen 18y ago
  I cringe to think what the developers at my work would do with threads in the Flash VM. I'd just as soon keep a single-threaded model.
  - dantheman 18y ago
    The single thread model has some serious limitations. For instance maybe you would like to load some images & then popup a component containing them. In a threaded world, you can have synchronous communication where it just waits till the download is complete before loading what depends on it. Right now you have to register callbacks, sure that's not too tough, but chaining like that makes it more difficult than it should be. download -> componentA > componentB > ComponentC whereas it might be easier to just go: CompnentA(file.download()); instead of file.Download (CompACallback, FaultCallback);
neovive 18y ago
This is a major point in favor of Flash. The adoption and expansion of Flash into the enterprise is critical to the future of Adobe. Thus, Adobe will continue to invest heavily on improving and expanding the Flash player, API, support and development tools. Microsoft could drop Silverlight with little impact on the company -- it's not critical to the success of Windows at this point.