Another massive advantage of HTML5 is that it allows developers to easily port applications to mobile. Now that every browser ships with native support for the standard, it has also largely replaced legacy platforms like Flash and Silverlight, thereby improving security and offering a seamless browsing experience.
In spite of its near-ubiquity, HTML5 comes with its own set of problems that trouble both programmers and end users alike. Primary among them is the lack of a standard HTML5 video format , but there are also other issues that remain a problem in what is otherwise the most reliable, secured and feature-rich web development platform.
Here are some of the disadvantages of HTML5: 1. Among the main formats, H. While some consider the continual upgrades to be an advantage, unexpected changes in the standard can render elements in a website useless until the admin issues a fix.
Another major hurdle is gaming support because the only scripting language supported by HTML5, JavaScript, is a less-than-ideal platform for a strong gaming experience. Custom name spaces, member access, interfaces, and inheritance, have problems under JavaScript, forcing developers to look for workarounds. That said, game developers have still moved from Flash to HTML5 because of seamless cross-platform support across all user-agents. HTML5 improves the way the web works, making it easier for developers to create great websites and for users to experience those creations irrespective of their device of choice or the browser they are using.
Recommended Articles 3 Comments Thanks a lot. This was exactly what I was looking for. This helps developers increase the online visibility of the website and attract highly targeted traffic thus improving the conversion rate. Your Comment. Stuck trying to diagnose connectivity or performance issues? Learn how to quickly get to the root cause of traffic and network problems.
While HTML5 is a draft standard, its ultimate role as the dominant cross-platform solution is a fait accompli.
Basically, Silverlight and HTML5 both have their place and purpose, as a close look at the similarities and differences of the two tools will reveal. The similarities are tied to ease of deployment, the richness of the user interface, and the interaction model. One of the concerns with the desktop, especially for Windows developers working within the Windows environment, is deployment. This is an issue for those working in mid-sized to large companies.
The deployment footprint for desktop applications is quite troubling for them because they have to ensure that a certain version of the runtime is available, and they have to get updates to every machine.
Therefore, deployment has been a pain point for richer desktop applications. In some cases, the business reasons for sticking to desktop applications will continue: better performance and better use of native hardware—simply getting things done in an easier, more seamless manner. Plus greater programmer knowledge exists for development scenarios on the desktop platform.
These reasons can override the need for easy deployment. Such concerns must be balanced as alternative solutions are explored. In general, both Adobe Air and Silverlight are good solutions. Within the Microsoft stack, Silverlight is a very good solution, because even though there is a runtime, it is structured for seamless deployment and it is easy to get users updated. Essentially, Microsoft takes care of the updating experience.
HTML5 provides a similar deployment scenario; however, it has hidden traps because it relies on a browser. The team using an HTML5 solution has to be reasonably sure that their customers will have access to the latest browsers and will install them.
All mobile clients will support it in the future, even if they do not now. In short, while a small deployment difference exists between Silverlight and HTML5, the deployment model is basically seamless in both. In terms of richness of user interface UI , Silverlight has some advantages. To get a rich UI done quickly, Silverlight is probably a better solution. Soon it will have much more prepackaged content available to facilitate the building of rich UI environments. The two tools are also comparable in terms of their interaction models.
Neither demands that one wait for a page refresh, and working with either is similar to the way one works with a desktop application. The strong functional similarities between HTML5 and Silverlight tend to dissolve on closer examination. First, Silverlight is more suited for intranet applications that have relative control over the deployment environment than for true Web-based deployment.
If you look a little deeper at the deployment scenario in Silverlight, it is still not a true end-user solution. Is the customer going to have a system that can run Silverlight? Is it something that will be allowed? For example, if a user goes to Amazon.
For Web site use, the more seamless the experience, the better. However, in cases of an intranet solution—where developers have more control over the machines and know that they are Windows machines—they may not have quite the degree of control needed for a desktop application, but they know that those machines are capable of running Silverlight.
That provides the developer with a great deal of flexibility. Now he or she can choose to go with Silverlight; when compared to HTML5, it is definitely a more productive development experience. Microsoft has excellent tools that make it easy to build and deploy applications with Silverlight. HTML5 requires a bit more work while Silverlight is more structured—the tools are in a class of their own. This is further supported by the quality of Silverlight tools, which empower the developer to build Silverlight applications in a quick, drag-and-drop manner.
Silverlight also makes UI development, and most other development, highly productive by using the built-in control abstraction model and native controls that Microsoft has provided. HTML5 on the other hand requires support from your current web-application tool. If you are developing in ASP. NET, that would be Visual Studio. NET, which doesn't provide any tooling support for HTML5, as is probably the case with many development platforms currently.
Programming language is another consideration. It goes back to the tooling and the nature of the language. JavaScript is a different beast to work with; even experienced JavaScript programmers know that it is a bit harder to understand because it is a procedural, type-unsafe language by nature, whereas C is an object-oriented, type-safe language.
This basically means that large sets of code are better written and maintained in C than in JavaScript. Silverlight is limited if mobile deployment is required. Currently, Silverlight is only supported on Windows Phone. It may be supported on other platforms in the future, but this is not certain. Currently, to develop a Silverlight application that mobile clients can use, the Windows Phone device must be mandated.
Over the last few months, Microsoft implemented a hardware solution for Silverlight 5, so it may offer a slight performance advantage over HTML5 on newer machines.
IE9, for example, does a lot with HTML5, so this performance difference is more transitory than decisive. Notably, HTML5 is a standards-based environment, something of great concern to some developers but of little concern to others.
In many cases there is a push to adhere to standards, so that if things change, the migration path is easier. HTML5 is standards-based and about as global as it gets. Silverlight has a considerable advantage over HTML5 in that 90 to 95 percent of code can be shared with desktop applications. In HTML5, developers can keep the UI separate and have a business layer; however, a great deal of UI code has to be written on the two platforms, which takes more effort and allows almost no code sharing.
In the end, the tools must be selected with a clear goal in mind to avoid the confusion Einstein identified. For example, developers may be comfortable with WPF and Silverlight and so choose that path, but after exploring what they want to do with the application, they may hope to launch a mobile client within six months to a year. With those features, Silverlight will ultimately provide a richer Internet experience.
In the meantime, the Flash platform will continue to deliver a ubiquitous, consistent platform that enables ever richer, more engaging user experiences. Analyst Cote sees no immediate threat to these rich Internet app browser plug-ins: "It would take many years to reproduce the functionality in those plug-ins.
Google's Fette agrees. HTML5 is only a starting point, he says, and companies such as Google will add their own advancements, such as the ability to drag and drop images to a browser. A few industry players may be conflicted Most companies involved in the HTML5 effort are browser developers or rich Internet application tool developers, but not both. The exception is Microsoft, which therefore is in a difficult situation, says Almaer. The company has heavy investments in trying to propel Silverlight to dominance.
Google may also face some touchy decisions. Paul Krill is an editor at large at InfoWorld, whose coverage focuses on application development. Here are the latest Insider stories.
0コメント