Re: Developer Use of Visual Basic Plummets

Paul Clement wrote:
On Sat, 16 Dec 2006 04:05:49 +1100, "aalaan" <aalaan@xxxxxxxxxx>
wrote:


¤ And how do I know they won't do the same again when I've
¤ gone the learning process all over again?

There is no way to know whether Microsoft will change the product
significantly again. There are no guarantees because development
tools change, or they die. But what is known is that Classic Visual
Basic *is* dead with respect to future development.

So is COBOL. I keep seeing job ads for it though...

¤ Finally, I note NET seems to
¤ call itself Visual Basic too. A bit confusing?

Why is it confusing? Have you been listening to those folks who don't
use it, call it a different language?

Well I use it. In fact, I use both VB Classic and VB.NET in a commercial
environment. And they most definately are different beasties. Oh, some
syntax may be the same, but syntax is a very small part of a language.

It most definately is confusing. Just have a scan through this newsgroup
for people posting questions about "VB", and after half a dozen posts, we
finally realise that we are offerring VB Classic solutions to their VB.Net
problem. Just have a listen to bosses who keep talking about "upgrading"
(not rewriting) apps to VB.Net. This is a confusion that Microsoft, and
IMO, yourself, are deliberately creating. Stuff all the little fish, lets
stir up the mud on the bottom again.

Note that this has nothing to do with which language is better, that's not a
discussion I am having. The point is that the languages are different, and
should not have been given the same common name. I could handle VB.NET
2005, but not VB 2005.

--
Regards,

Michael Cole


.

Relevant Pages

  • Re: VB6, VB2005, or Something Else?
    ... ¤>¤ after we had hundreds of thousands of lines of code in place already. ... The point should also be made that Microsoft didn't actually /have/ to break our ... you've set up your own version of your own "truth". ... ..NET onto the Visual Basic Classic language and retain a good deal of backwards ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤>¤ investment. ... ¤>No I'm sure Microsoft didn't have to do a lot things that broke code. ... supporting unique features of the language. ... probably one of the few who continue to work with and support both versions of the product. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤> Gloating? ... The "putting it out of it's misery" statement simply reflected its poor performance (which was never ... Microsoft simply didn't care about it and it was blatantly obvious, ... changes are made to the language or extensions to the language. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤> addressed) over the past decade. ... By the way, the preformance of Gosub in PCode was quite good, it ... Yes but Microsoft wasn't interested in fixing it. ... ¤> changes are made to the language or extensions to the language. ...
    (microsoft.public.vb.general.discussion)
  • Re: Developer Use of Visual Basic Plummets
    ... ¤ Paul Clement wrote: ... ¤> Why is it confusing? ... syntax may be the same, but syntax is a very small part of a language. ...
    (microsoft.public.vb.general.discussion)
Loading