Re: VB6, VB2005, or Something Else?

Paul,

The "putting it out of it's misery" statement simply reflected its poor
performance (which was never
addressed) over the past decade. Microsoft simply didn't care about it and
it was blatantly obvious,
over this period of time, to anyone who used it.

The "putting it out of it's misery" statement certainly sounds like
gloating. By the way, the preformance of Gosub in PCode was quite good, it
was only in compiled code that it slowed down. And, unless it was used in a
tight loop, that slowness could not be percieved.

There is even a KB article that dates back almost
nine years which recommends using alternatives.

Cite?


¤ > It doesn't work because language features change, new features are
added.
¤
¤ Are you listening at all? It does work, and can be done.
¤

Well obviously it doesn't or you wouldn't be having any issues doing it.
It only works if *no*
changes are made to the language or extensions to the language. Now how
realistic is that?

I'm not complaining about the necessary changes, I'm complaining about the
unnecessary ones.

¤ > But for some reason you're
¤ > again insistent upon continuing to work in a way that will cause you
¤ > trouble.
¤
¤ I work in a way that saves me time. Time is very valuable. There is
always
¤ trouble in programming. That's what we do, solve problems. My complaint
is
¤ that Microsoft intentionally and unnecessarily made it more difficult.
¤

All that I can say is that I've worked with Microsoft applications and
development for years. I've
never operated backwards with respect to application versions. In my
experience you always encounter
problems because that is simply the nature of the upgrade. It isn't even
disputable unless you
expect software features to stand still.

Until now it wasn't necessary. The problem is that now they have cut off a
forward path for our VB6 code, so now it has become necessary to innovate.

Well in that case there should be a suitable replacement.

There is, it's called C#.

If Microsoft recommends I use something
different several years prior to it's demise, as they did for GoSub, then
I think that's fair.

Could you give us some insight as to how clear Microsoft's recomendation
was? I am sure that stronger things have been said in favor of C# and
against VB.


¤ > When is VB going to be thrown out?
¤
¤ How long before GoSub got the axe was it announced?
¤

That would have been in the next version. So if they haven't announced it
for the next version then
according to your logic Visual Basic lives on. Perhaps after that it will
be thrown out.

Could you clarify that? I would like to see the announcement about GoSub.

Do you want
to go on the record for that prediction?

No, I want to go on record as a discontent client of Microsoft.


Well it's not about investment into the languages. It's about investment
into the platform. The more
choices they provide for .NET the more likely they are to draw investment
from other sources, and of
course most importantly, their customers.

In any event I think you're the first person I've ever heard draw a
parallel between GoSub and the
Visual Basic language as a whole. I think even Chicken Little would be
scratching his head over this
one. ;-)

In a letter to the editor of a recent edition of VSM (Vol. 16, No. 3) it
was stated: "I believe you should try to move to C# and drop Visual Basic
altogether."

That is not the first time that I have read similar statements...

Gary


.

Relevant Pages

  • Re: VB6, VB2005, or Something Else?
    ... Microsoft is the source of my pain. ... We were talking about GoSub, but porting the code requires a lot more than ... ¤> ¤ future. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... Microsoft is the source of my pain. ... We were talking about GoSub, but porting the code requires a lot more than ... ¤> ¤ future. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... Since Microsoft has taken it upon themselves to clean up VB, ... ¤ As to Microsoft, I think where they went wrong was to consider VB6 ... The problem is that we are programmers. ... We will be complaining for a long time to come. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤>> The Do...Loop that tests the condition at the top is no more capable ... ¤>> alternate between the two without a change in functionality. ... GoSub isn't even remotely comparable ... also remember there was a fair amount of outcry when Microsoft simply changed Wend to End ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤> doing that would be. ... ¤> ¤ programmers like novice users. ... Complaining may make you feel better but the ... Microsoft MVP ...
    (microsoft.public.vb.general.discussion)