> Certainly all past efforts to "rehabilitate" the language have failed in
the
> reputation sense, perhaps this next move will fail, and hurt .NET with it?


I hope your wrong, but I this does have me shaken.

Even if .Net is successful, C# will get all the credit. We need to get the
word out that VB is powerful enough for business use. When it comes right
down to it VB.Net is still easier than C#, which makes us more productive.
But if we can't get the companies to recognize that, we are still out of a
job.

--
Jonathan Allen


"Michael (michka) Kaplan" <former_mvp@spamfree.trigeminal.nospam.com> wrote
in message news:3a71cfdc@news.devx.com...
> Many people here have been discussing the issues surrounding the need for
> change, to move VB forward, to help fix up the reputation problems that VB
> has had.... and either stating or at least hoping that VB.NET will do

this.
>
> But what if they are wrong? What is the reputation VB has where VB
> developers feel like they must defend themselves no matter where they go
> (even Microsoft!) actually follows VB.NET? This is a very strng

possibility.
>
> And what if this hurts the CLR overall, by association? Somewhat less
> likely, but still possible, I think.
>
> Certainly all past efforts to "rehabilitate" the language have failed in

the
> reputation sense, perhaps this next move will fail, and hurt .NET with it?
>
> Thoughts, anyone?
>
> --
> MichKa
>
> a new book on internationalization in VB at
> http://www.i18nWithVB.com/
>
>
>