Re: When will MS Stop supporting VB?

From: Ken Halter (Ken_Halter_at_Use_Sparingly_Hotmail.com)
Date: 09/07/04


Date: Tue, 07 Sep 2004 12:46:23 -0700

Chad Lane wrote:
> There are 3 million plus VB Programmers in the world and Microsoft knows
> this, so it is doubtfull that VB.NET will ever be dropped.

It was also doubtful that they'd break VB code.

"The probability of MS _deliberately_ making a language change that
breaks lots of existing code is almost zero"
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=%23Yby16MF%24GA.252%40cppssbbsa05

Funny that "is almost zero" turned into "is guaranteed"

> What is dead is the old VB way of doing things everything prior to
> VB.NET, even parts of the Visual Basic Namespace in DotNet will fade

Yep... dead alright. For no good reason. There's also no good reason for
that "wizard" to dump all File IO routines on the floor. I guess .Net
*might* know what to do with it if it were the hideous FSO but since
it's not smart enough to know what to do with...

Open SomeFile For Input As SomeNumber

...I guess it's the idiot VB (and all versions of basic prior to VB6)
devs that are making the mistake of putting that "Old" code in their
apps. How could we've been so stupid! We should've known right away
that, even though it's 25% as fast and full of bugs, we should've used
the FSO!!!

> away eventually(at least the backwards compatible syntax code like the
> old MSGBOX, it's my understanding it is there for backwards
> compatibility.

Oh boy... at least we can show a msgbox... whoopie...and "Fade away"?
Doesn't that make the code even more unstable?

> In my opinion I am glad that VB will lose people who don't like or can't
> understand OOP development, these are the same people writing unreadable
> VB Classic code.
>
> Let me ask you all this question How can C# be any better then any other
> language in DotNet if they all use the same CLR?

Wrong group. .Net questions belong in .Net groups.

btw... poke at a few of Applemans articles for more info on "standards"

"With Visual Studio 2005 it seems clear that Microsoft has
effectively abandoned the CLS in favor of a new standard:
specifically - the set of language constructs supported by
Visual Basic .NET and C#."
http://www.danappleman.com/index.php?p=11

RAD is not productivity
http://www.danappleman.com/index.php?p=4

Gotta love.... especially the last sentence.

<q>
And the bad code is?
And by the way, it may be time for us to reconsider our definition of "bad"
code as well. It's the beautifully structured, object oriented,
"good" C++ code that's giving us all huge amount of grief due to
security problems (buffer overruns, memory leaks, games with pointers,
etc.). Barring use of Win32 API calls, VB6 was remarkably immune to all
of these problems. Makes you wonder who's been writing the bad code,
doesn't it?
</q>

...and finally, for all of the "OOP development" freaks out there. imo,
switching to event driven code's going to cause far more confusion to
procedural programmers than anything related to OOP.... and that IDE...
can you spell BLOAT? It belongs in the Interface Hall of Shame with
every other 99 tab application. Might as well release an OS that's
specifically designed to write .Net apps. (or maybe that's part of that
20+ mb framework that everyone has to have installed to even get Hello
World to run)

Interface Hall of Shame - Tabbed Dialogs -
http://digilander.libero.it/chiediloapippo/Engineering/iarchitect/tabs.htm

-- 
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..


Relevant Pages

  • Re: Disappointment in VC++ .Net in VS2008
    ... if that is what they felt was the way to support .Net. ... C++/CLI is not C+, it is Microsoft's own extension purely to accomodate .Net, and they can change the language at will to acoomodate new .Net features as they like. ... I argued that C++/CLI ..Net programmers have been totally let down by the VC++ team, and even that this was Microsoft's plan from the beginning. ... We both know that Microsoft has enough resources to do this, ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Disappointment in VC++ .Net in VS2008
    ... language to accomodate new .Net features, if that is what they felt was ... front end to support a better Intellisense, ... C++/CLI programmers. ... We both know that Microsoft has ...
    (microsoft.public.dotnet.languages.vc)
  • Re: About .NET strategy
    ... C# isn't the biggest programming language for .NET. ... There are more VB programmers than C programmers. ... there is a pool of folks which Borland has which Microsoft ... Today, Microsoft controls C#. ...
    (borland.public.delphi.non-technical)
  • Re: Visual Basic to be discontinued in 2008??
    ... Robin S. ... thousands of VB.Net programmers around the world don't agree ... All people see is the language and abuse, ... point them in the right directon (away from Microsoft Visual Basic - ...
    (microsoft.public.dotnet.languages.vb)
  • Re: OT: Why is C so popular?
    ... C programmers hate Pascal. ... Computers became ever cheaper and more widespread; ... in the jobs market to have certificates of Microsoft indoctrination. ... for creativity can never be entirely suppressed - were in an ideal ...
    (Debian-User)