Silverlight vs. Flash: Difference between revisions
imported>Paul Nikolas Phoa |
imported>Ganggang Hu |
||
Line 71: | Line 71: | ||
=== Programming tool === | === Programming tool === | ||
[[Microsoft]] provides a handful amount of programming tools to support its [[Microsoft Silverlight|Silverlight]]. Visual Studio 2005 (supports Silverlight 1.0) and 2008 (supports Silverlight 1.0 and Silverlight 2.0), and Expression Studio are the main programming tools that developers can use to build Silverlight animations/applications. Adobe also provides its own developing tools to assist developers in creating Flash animations/applications. Such tools are Adoble [[Flash]] and Adobe Flex. | [[Microsoft]] provides a handful amount of programming tools to support its [[Microsoft Silverlight|Silverlight]]. Visual Studio 2005 (supports [[Microsoft Silverlight|Silverlight]] 1.0) and 2008 (supports [[Microsoft Silverlight|Silverlight]] 1.0 and Silverlight 2.0), and Expression Studio are the main programming tools that developers can use to build [[Microsoft Silverlight|Silverlight]] animations/applications. Adobe also provides its own developing tools to assist developers in creating [[Flash]] animations/applications. Such tools are Adoble [[Flash]] and Adobe Flex. | ||
Users can reuse [[C# Programming Language|C#]] classes from their tool inside exported contents. However, there is no development environment for creating [[Flash]] desktop applications which is based on [[ActionScript]]. In [[Flash]] route, users have to write all the classes and objects twice to keep pace with the tool changes. They need [[.NET Framework |.NET]] classes to handle the author time experience and [[Flash]] classes to handle the run-time. If there are [[Web server|server]] components, users need to switch back to [[.NET Framework |.NET]] and discard all the classes that the run time is using. | Users can reuse [[C# Programming Language|C#]] classes from their tool inside exported contents. However, there is no development environment for creating [[Flash]] desktop applications which is based on [[ActionScript]]. In [[Flash]] route, users have to write all the classes and objects twice to keep pace with the tool changes. They need [[.NET Framework |.NET]] classes to handle the author time experience and [[Flash]] classes to handle the run-time. If there are [[Web server|server]] components, users need to switch back to [[.NET Framework |.NET]] and discard all the classes that the run time is using. |
Revision as of 17:07, 17 August 2008
With the rocket development of Internet, the techniques used for building web pages is improving all the time, which not only brings people more information but new experience of surfing on the Internet. Many techniques have been applied to enrich the web page these years, from totally the plaintext in early 90's, first to web page with pictures and then that with embedded sounds. Later, Sun Microsystems proposed Java Applet, which was popular for not long time until being conquered by Adobe Flash. Now Microsoft proposed Silverlight technology. Some people say that Microsoft made a wrong decision while others claim that Silverlight will kill Flash at last. According to the next step in the value chain, for Flash, it focus on building rich applications with Flex. For Silverlight, Ajax is becoming the way to add more value.
So, Silverlight and Flash ---- Who is going to win?
Technology
When it comes to general technology features, both Flash and Silverlight have the same functions and benefits as follows:
- Rich 2D animation/graphics with audio and video
- Choice of standards-based and high-performance languages
- End-to-end server and application platform
- Client side playlists for ad-insertion
- Robust video publishing tools
- High-performance, multi-core enabled lightweight client
- Data exchange with web server
- Easy installation support for platform requirements
- Tools product line integrity
- Multiple browsers support such as IE, Firefox, Safari and Opera
On the other hand, both of them have their unique features. For example, Flash has offline document support, rich set of control library and test tools. While Silverlight has hardware-assisted editing and encoding solutions, XML-based presentation for SEO, and content access protection (DRM).
Animation manipulation
Flash is frame based, which requires users to compute the duration of an animation. For example, there are 12 frames per second in Flash animation model. If users want an object to move 5 seconds continuously, they need to calculate how many frames 5 seconds will take. Also, the player doesn't maintain any frame rate unless users embed blank audio tracks.
Instead of frame based, Silverlight supports the time based WPF animation model, which allows users to define the start and end conditions without calculating positions on various frames. Then Silverlight can generate animation process automatically.[1]
Additionally, when create animation, the Adobe suite of products can easily share objects and files between applications such as Illustrator, Flash, Dreamweaver, Photoshop, etc. While Silverlight has these options built into it already along with several other tempting products such as ad-insertion and free streaming solutions.[2]
Video codec and audio decoder
Flash supports multiple video formats with high quality codec and nice bandwidth usage, such as scalable full screen video up to HD(720p). The price of its media server licensing(unlimited bandwidth) is only one forth of that of Silverlight. But except that its Sorenson’s proprietary H.263 implementation is loosely based on a standard, Flash has no industry standard video codec yet. Also, the audio formats Flash supports are all proprietary, except for MP3 and ADPCM, whose quality of compression is not so impressive, and still requires licensing fees and third party conversion libraries.
Compare to Flash, Silverlight implements industry standard VC-1 codec for video, as well as offering support for WMV and WMA. Microsoft makes available a free Encoder SDK for producing WMA and WMV so that people are able to encode by themselves with easier integration and cheaper cost.
Here is a comparison of video codec between Flash and Silverlight using different computer systems.[3]
Flash VP6E | Flash VP6S | Flash H.264-High | Silverlight | |
---|---|---|---|---|
PowerMac Dual 2.7 GHz PPC G5, OS 10.4.11, FireFox, Flash Player 9.0.115.0, SL 1.0.30401.0 | ||||
Processor(percentage of 2 processors) | 72.0% | 66.3% | 85.8% | 108.0% |
Drop frames | no | no | yes | yes |
Estimated frame rate | full | full | 5-6 fps | 1-2 fps |
Drop audio | no | no | yes | no |
HP xw4100, 3.0 GHz P4 with HTT, Windows XP, FireFox Flash Player 9.0.124, SL 1.0.30401.0 | ||||
Processor | 87.5% | 97.1% | NA | NA |
Drop frames | yes | no | yes-stopped | yes-lost synch |
Estimated frame rate | 2 fps | full | stopped | 1 frame/3 seconds |
Drop audio | yes | no | yes | yes |
HP 8710P, 2.2 GHz Core 2 Duao, Vista, IE, Flash 9.0.124.0, SL 2.0.30226.2 | ||||
Processor | 51.9% | 52.0% | 34.8% | 47.3% |
Drop frames | no | no | no | no |
Estimated frame rate | full | full | full | full |
Drop audio | no | no | no | no |
Dell Precision 390, 2.9 GHz Core 2 Duo, XP, IE, Flash 9.0.124.0, SL 2.0.30226.2 | ||||
Processor | 22.7% | 17.5% | 7.7% | 26.0% |
Drop frames | no | no | no | no |
Estimated frame rate | full | full | full | full |
Drop audio | no | no | no | no |
Binary or text file
Flash stores shapes using binary shape records. In order to write shape definitions, users need to either license a third party Flash file format SDK, or build libraries by themselves. While Silverlight uses text based XAML, which can be output using an XML object. So users don't need to buy special libraries or write their own libraries.
Flash stores fonts glyphs using the same exact shape definitions that are used for any other shape. The player does not understand TTF files, so users need to use the Win32 APIs to figure out intricacies of fonts in the Flash file format documentation by themselves. But in Silverlight, WPF/E lets users embed true type font information directly into projects, and download that information with the downloader object without doing extra work.
However, with the capability of compiling down into a binary, Flash can actually starts executing before it is fully downloaded, which is one of the serious benefits to using binary SWF and more satisfying than the pure text files in Silverlight, which brings the runtime from zero to hero before one can do anything. Furthermore, Flash has plenty of functionality encapsulated in the runtime. It has its own JIT compiler, its own language ActionScript and a healthy set of controls. But Silverlight uses JavaScript as the scripting language and depends on the browser for most of the interaction processing.
Platform support
Flash integrates with multiple platforms and languages. It supports Windows, Max OS X, Linux and also moblie platforms. While Silverlight has some limitations on this aspect. It mainly supports Windows and Max OS X. Silverlight looks to be as far as Microsoft has ever gone as a company to embrace cross-platform and yet they still fail to support Linux.[4] However, a newly developed project called Moonlight by Mono open source project sponsored by Novell allows Linux users to run Silverlight applications on Linux, provide a Linux SDK to build Silverlight applications and reuse the Silverlight engine built by Mono for desktop applications. [5] Written with a combination of C++ and C# code, Moonlight for Linux Supports Silverlight 1.0 was first released in May, 2008.[6] Also, Silverlight is spreading to mobile platform by building various applications on mobile devices. The only hope for Silverlight is to make the runtime open source and cherish the hope for consistent cross-platform support, though Microsoft has a terrible cross-platform track record as a company and most of the company's prior efforts have been deprecated.[4]
Programming tool
Microsoft provides a handful amount of programming tools to support its Silverlight. Visual Studio 2005 (supports Silverlight 1.0) and 2008 (supports Silverlight 1.0 and Silverlight 2.0), and Expression Studio are the main programming tools that developers can use to build Silverlight animations/applications. Adobe also provides its own developing tools to assist developers in creating Flash animations/applications. Such tools are Adoble Flash and Adobe Flex.
Users can reuse C# classes from their tool inside exported contents. However, there is no development environment for creating Flash desktop applications which is based on ActionScript. In Flash route, users have to write all the classes and objects twice to keep pace with the tool changes. They need .NET classes to handle the author time experience and Flash classes to handle the run-time. If there are server components, users need to switch back to .NET and discard all the classes that the run time is using.
Unlike Flash that is largely built for graphic designers, Silverlight allows users to create contents with the same tools they use on a daily basis (such as Visual Studio .NET) in order to keep all the code for the server, the authoring tool, and the run time/player components inside the same project.
As for the learning curve, HTML, Javascript and Ajax developers will probably feel more familiar to Silverlight. WPF/E builds upon the same development paradigm that web developers have gotten accustomed to, while the Flash, Flex and ActionScript field requires a fair amount of re-learning. [7]
However, compare to Adobe, who has a deep cultural understanding of the creative process and strong experience with cross-platform support, the lack of experience with designer tools and inability to truly understand creativity of designers will be Microsoft's inevitable obstacle, which may cut out large percentage of designer market.
Market
According to a survey given by Adobe System in June 2008, 99% of computer users have installed Flash Player. But until then, there was still no official statistics about Silverlight given by Microsoft.
This significant difference of market share between Flash and Silverlight may due to following reasons:
- Silverlight was released as 1.0 in 2007 while Flash 1.0 was released in 1996. Flash already has sufficient time to grow, thrive and dominate the media plug-in market before Silverlight was born. One way for Microsoft to increase the number of Silverlight users is to include Silverlight in Internet Explorer.
- Users choose to view content built in Flash and therefore need the plug-in. Since Silverlight is still new, there is relatively little knowledge of its existence (among non developers) and application created in it. Microsoft is providing more Silverlight content, such as the NBC online 2008 Olympic Games.
Although Silverlight has many advantages over Flash, it pales in front of Flash in terms of availability. It is not a unique Microsoft problem but a problem for every new offering when there is an incumbent who has a majority market share. Because Flash is so ubiquitous that it pushed QuickTime, Real Player, and windows movie files right out of the web space. As a juvenile in market, Silverlight may need a long time to get acceptance for itself.
Comparison
Based on previous discussion, here is a table including technology and market comparison between Flash and Silverlight.
Silverlight | Flash | |
---|---|---|
Animation manipulation | time based | frame based |
Video codec | industry standard VC-1 codec | no industry standard |
Audio decoder | MP3,WMA,WMV | MP3 |
Binary or text file | XAML Text based & XML object | SWF binary shape records |
Platform support | Windows,Max OS X,Linux (in development), Mobile (in development) | Windows,Max OS X,Linux, Mobile |
Programming tool | JavaScript,VB.Net,C# | ActionScript |
Market | developing | rapid |
At least for the short term, Flash will continue to dominate the market because designers are more comfortable and familiar with the Adobe suite and Adobe is getting better all the time. Also, advertisement platforms are likely to run Flash advertisements because they wish people to see their advertisements without having to install new software. From distribution aspect, Flash currently has an in-browser installer where users don’t have to restart the browser and can refresh the web page once it’s installed. But Silverlight has a downloadable installer to let users close and then restart the browser, which is not so convenient. In order to win, Silverlight must own innovative technologies and excellent strategies to provide better design integration and easier distributed way to win over the design community. In short, it is a long-term battle.
See also
Reference
- ↑ Ezell, Jesse. "Silverlight vs. Flash: The Developer Story"
- ↑ Woelker, Jeff. "Adobe Flash versus Microsoft Silverlight Comparison ~ Flash Wins for the Short Term"
- ↑ Ozer, Jan. "Silverlight vs Flash: Video Codec Comparison"
- ↑ 4.0 4.1 Ted. "M$ Silverlight vs. Adobe Flash Player: 'Begun the clone war has...'"
- ↑ "Mono-Moonlight Official Webpage"
- ↑ LaMonica, Martin. "'Moonlight' makes progress on Silverlight for Linux"
- ↑ Ziade, Richard. "Flash, Silverlight & The In-Between OS"