Letters from Readers

Reader Letters: Reacting to Windows 8 Developments

Andrew Brust's November Redmond Review column, "Windows 8: Times Are Changing for Developers," got reactions from readers, many of whom are still troubled about what lies ahead.

It strikes me that what Microsoft did is level the playing field -- that HTML5, C++ and .NET all are equal in the Windows 8 landscape. Now we'll see how well they do one way or the other. Each has its own challenges -- I don't think the JavaScript engine (aka Chakra) is anybody's dream solution, either. That being said, sometime in the future we might look back on this moment and say, "This was the beginning of the end for .NET."

Richard Campbell
Canada

Our achievements must be disrupted in order for us to prosper -- really? So we have to go back 10 years to pre-.NET just because of this mistaken premise? Just to be clear: writing spaghetti and unmaintainable JavaScript mangled with HTML is absolutely not the way developers want to build business applications for Windows.

Garry
Cambridge, United Kingdom

How much does it pay, this cranking out of nonsense as [a] Microsoft apologist? The truth remains that Redmond has lost its way, having run off to chase this latest false messiah, HTML5/JavaScript, all as a result of that which was Steve Jobs' greatest coup of all time, having justified his bias against Flash with false statements about HTML5 and JavaScript being the future. The most exceptional and incredibly immersive user experiences on the Web are still created via Flash, and for as long as it lasts, Silverlight. Other than insulting the intelligence of those who already know this to be the case, no amount of Redmond propaganda will create the mass delusion for which they're hoping. Looking so forward to something worthwhile rising from the ashes in Redmond once Nero's done playing his fiddle...

Anonymous
Posted Online

This all sounds great, .NET lives on … What's hiding under the covers, though, is that they're stripping out fundamental capabilities on which developers rely. For example, do you want to connect up to the databases running your off-the-shelf-package apps? Sorry, buddy... you can't do that. Don't believe me? Read this.

Jamie Thompson
Posted Online

Visual Studio Magazine wants to hear from you! Send us your thoughts about recent stories, technology updates or whatever's on your mind.

E-mail us at [email protected] and be sure to include your first and last name, city and state. Please note that letters may be edited for form, fit and style. They express the views of the individual authors, and do not necessarily reflect the views of the VSM editors or 1105 Media Inc.

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