A Dianne by Any Other Name

This month readers weigh in on Mort and switching to C#.

Letters to Visual Studio Magazine are welcome. Letters must include your name, address, and daytime phone number to be considered for publication. Letters might be edited for form, fit, and style. Please send them to Letters to the Editor, c/o Visual Studio Magazine, 2600 El Camino Real, Suite 300, San Mateo, CA 94403; fax them to 650-570-6307; or e-mail them to [email protected]. Note that the views expressed in the letters section are the opinions of the letters' authors, and do not necessarily reflect the opinions of Visual Studio Magazine or those of 1105 Media.

A Dianne by Any Other Name
As a longtime VB developer, I read Patrick Meader's column, "A Mort by Any Other Name …" (Editor's Note, June 2008), with great interest. I agree that the overall attitude toward VB developers is reflected in the persona. But let's not stop at coming up with a new persona name; it's time for the developers to reflect the audience as well. I vote that the next developer persona should be Kathy, or Jen, or maybe even Dianne!

Dianne Siebold, posted online

Meader's column was interesting, but also another reminder of how VB programmers have been treated for a long time.

Too little credit is given to the ways in which VB's natural, English-like syntax helps you get the job done. One of my employees recently switched his major to computer science. His first class required some simple C programs that he wrote in Visual C++ with VS 2008. I found it interesting that even the VS 2008 IDE often laid out his code improperly, inserting a stray semicolon here, dropping a brace there, and so on.

At least VB looks like English. Our VB applications are in use worldwide, and we manage to pay the bills without knowing what { } means, and without having to remember if we have to put a semi-colon at the end of this line or the next one to make the program work logically.

Rick Lederman, received by e-mail

I suspect someone has mentioned this already, but it should be pointed out that "Mort" is French (or other Latin roots) for "Dead." No doubt, there is some subconscious derogatory energy being transmitted and possibly received in that regard!

Steve Fitzgerald, received by e-mail

Reluctantly Adopting C#
Patrick Meader's editorial on the would-be first-class status of VB strikes a nerve (Editor's Note, "Is VB Least Among Equals," April 2008). There's no way Microsoft can convince us that it regards VB as a first-class programming language, given the overall lack of support for VB in all Microsoft's new technologies that matter. As a VB programmer for more than 20 years, I have found myself gradually moving into C# (reluctantly). If Microsoft is serious about VB, it has a funny way of showing it.

Sayomi Olawumi, received by e-mail

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