Letters from Readers

Letters: Readers Sound Off About HTML5

Robby Ingebretsen's July VSInsider column on HTML5 produced plenty of opinions.

Robby Ingebretsen's July VSInsider column on HTML5 produced plenty of opinions:

To be honest, I wouldn't say HTML5 is going to replace things like an app made in C++, but it's definitely not the hype that was Java. HTML5 -- or, more specifically, Web apps -- is real and is not going away. More and better app processing is happening on the client, even data stores.

Name Withheld

Microsoft did not get to where it is today by developing open source (or TML/JavaScript) development platforms. It also did not get where it is by cowering to the open source (or HTML/JavaScript) crowd. Silverlight is a reliable and elegant platform. This is what the company should be pushing.

John

The reason why Microsoft platform developers are overwhelmingly rejecting all the hype about HTML/JavaScript as a replacement for a "real" development environment (like we already have in the XAML/CLR languages/.NET technology stack) is because the HTML/JavaScript stack is so fundamentally lacking in the basic things we've come to depend on to create "real" applications. A partial list of big ones includes: state, object orientation, tooling, strong data typing, data binding, compilation, LINQ, the Entity Framework, Windows Communication Foundation, Windows Workflow Foundation and (at least up until recently) support from an organization (Microsoft) committed to advancing the platform's technology with a consistent level of quality and dependability while supporting its developers with a firehose of different media, online resources and events.

A complex application's UI is like the tip of an iceberg: There's much more below the surface than above. The typical HTML application is more like a sailboat: What's above the waterline may be pretty, but there's not much underneath. I wish the bigwigs at Microsoft pushing this travesty and the ignorant media types mindlessly parroting them would spend a little time understanding this.

Bryan Morris

Peter Vogel, VSM tools editor, offers a response:
Here's a question: Do you want to deliver your functionality to someone who's running on a non-Windows platform? If the answer is "No," then the .NET technologies are an excellent choice. If the answer is "Yes" (which means 95 percent of the smartphones out there), then the technologies you need are HTML and JavaScript. This assumes, of course, that you get to pick your arena: Your customers, clients or employer may disagree with your choice.

About the Author

This story was written or compiled based on feedback from the readers of Visual Studio Magazine.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube