Comparing HTML5 to SL5
Comparing HTML5 to SL5
Join the DZone community and get the full member experience.Join For Free
Learn how error monitoring with Sentry closes the gap between the product team and your customers. With Sentry, you can focus on what you do best: building and scaling software that makes your users’ lives better.
This is a real gem of an article that outlines a core comparison between HTML5 and SL5.
Here’s how it opens:
The good news is the SL remains a great choice.
And, here are the 7 parts I think LOB developers should read:
1. HTML 5 has no support for User Controls: HTML 5 does not offer any integrated solution for creating controls except basic copy/pasting of code. This is a big minus for business projects looking at industrializing their developments. We are far from the plethora of controls that can be simply referenced in Silverlight.
3. HTML 5 has weak Threading Support: HTML5 has the concept of Web Workers, threads that are independent from the main thread (the one that displays and manipulates the DOM). For Silverlight, communication with other threads is done by calling methods and passing parameters (in fact, nothing special). Silverlight outperforms Web Workers on potential and tools but also in terms of control over the threads. The addition of future technologies such as Async Framework will add even more power to Silverlight.
5. HTML 5 has weak Device Access support: Silverlight 5 provides access to the datastream from the camera or microphone. It can also send a print job controlling the drawing of each printed page. HTML 5 on the subject is currently a bit light in terms of access to the camera or microphone.On the topic of devices access, Silverlight 5 wins by a large margin (for now).
Read the whole article for yourself, here.
If I could throw in my 2 cents, I would add that we should all remember that HTML5 is really version1, while SL is version 5 and completely managed by Microsoft. As scary as that may sound, the reality is – infighting between browser manufacturers (which is inevitable) remains moot with SL. The power of data binding alone makes XAML-based applications a slam dunk for data-driven line-of-business apps.
Someday HTML 5 may be a better choice, but that’s someday and it may never come. Today, SL reigns. However, if you really are building line-of-business applications, consider WPF. If SL dwarfs HTML5, then WPF dwarfs SL – and they are both Managed Code and XAML-based. WPF has more controls, richer binding options, animation options, trigger options, and so much more. Take a look.
Note: Please read that I said line-of-business applications! General and public web sites are not the same story. Their needs for managing data, eventing and threading are far less. For those sites, do not ignore the reality of HTML 5. It is (and will grow more) powerful and is very likely your absolute better choice.
Opinions expressed by DZone contributors are their own.