Re: Wish I was using .net

Ken,

I think you hit the proverbial nail on the head with regards to the MS VB
Development team.

Mike.

"Ken Halter" <Ken_Halter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Ogg0ATjNGHA.1032@xxxxxxxxxxxxxxxxxxxxxxx
"Michael D. Ober" <obermd.@.alum.mit.edu.nospam> wrote in message
news:%23Dz0ZKjNGHA.1760@xxxxxxxxxxxxxxxxxxxxxxx

I just wish MS hadn't thrown out the baby with the bathwater when
modernizing VB 6. As may people in this NG have correctly pointed out,
MS
made a lot of changes to the VB language that break a lot of existing
code.
I suspect many of these changes were unnecessary, despite the
protestations
of the MS VB development team.

Mike Ober.

Actually, it's the MS VB dev team that put us in this mess. They're the
ones
that did and want to be able to make future changes on a whim (depending
on
the flavor of their starbucks that day)

Will VB ever be standardized?
"C# has been submitted and approved by the ECMA, will Visual Basic ever be
submitted?"
"Well, never say never, but there are no current plans to submit Visual
Basic to a standards body."
http://www.panopticoncentral.net/archive/2005/12/30/10911.aspx

...and, if you look at the language spec for VB2005, you'll see that the
language they used leaves this "I changed it because I can" rule intact.

"The information contained in this document represents the current view of
Microsoft Corporation on the issues discussed as of the date of
publication.
Because Microsoft must respond to changing market conditions, it should
not
be interpreted to be a commitment on the part of Microsoft, and Microsoft
cannot guarantee the accuracy of any information presented after the date
of
publication.
This Language Specification is for informational purposes only. MICROSOFT
MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION
IN
THIS DOCUMENT"

The main problem with the VB team is.... they don't use VB. Never have,
never will. (I'm sure someone'll pop in and say "you're wrong, look at
this
snip I wrote") Besides, they suffer from "all new team members" where one
team gets the boot and another takes its place and couldn't care less what
the previous team was doing. Too busy trying to be a Rock Star I guess....

NET Rock Star: Paul Vick

http://www.findarticles.com/p/articles/mi_zddvs/is_200404/ai_ziff124655/pg_2

--
Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm
Freeware 4 color Gradient Frame? http://www.vbsight.com/GradFrameCTL.htm






.

Relevant Pages

  • Re: Wish I was using .net
    ... ....and, if you look at the language spec for VB2005, you'll see that the ... Microsoft Corporation on the issues discussed as of the date of publication. ... Too busy trying to be a Rock Star I guess.... ... DLL Hell problems? ...
    (microsoft.public.vb.general.discussion)
  • Re: Open Post to the C# Development Team
    ... You might try posting to the MSDN forum for C#, or submitting your opinions via the feedback website. ... Posting a letter to the C# development team here is akin to posting a letter to Santa Claus. ... As language designers, you should probably pick a paradigm and stick ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Python does not play well with others
    ... development team for the language or the development team ... for the subsystem takes responsibility for making them work. ... community with the expertise to extend the language and libraries, ... usually the ones who've been happily using the polished features for ...
    (comp.lang.python)
  • Re: Test first as specification
    ... >>>alone is a fairly bold statement, and I would expect it to be ... >> A compiler can be specified through tests. ... >> A compiler is not a language. ... to allow a development team to hide in the closet while ...
    (comp.object)
  • Re: What I Think Delphi Needs to Do to Survive
    ... The downside with VB at this point isn't the language, ... AFAIK Win32 VB syntax hasn't changed has it? ... can ask the VB development team yourself, which I have done face to face. ... "Drop backward compatibility altogether. ...
    (borland.public.delphi.non-technical)