Re: VB6, VB2005, or Something Else?

Paul:

On Tue, 11 Apr 2006 08:12:47 -0500, Paul Clement
<UseAdddressAtEndofMessage@xxxxxxxxxxxxxx> wrote:

¤ > Then given what we have known for several years now, how would you
¤ > describe it?
¤
¤ I suppose because "what we have known for several years now", became know
¤ after we had hundreds of thousands of lines of code in place already. If we
¤ had been well informed well before writing all of that code I believe it
¤ would be a different case. At any rate, even code with no GoSubs does not
¤ easily convert to .net, so I don't really see your point.

Point is that you've had several years now to decide what to do. If you think that continuing to
complain about it for the next five years is going to help then I have some bad news. That may sound
harsh and it may be unfortunate but that's the reality of it.

The point should also be made that Microsoft didn't actually /have/ to break our
code. That may sound harsh, but unfortunately, that's the reality of it -
they've broken our existing code and disregard our intellectual property
investment. Advertising that Microsoft is dropping support for VB Classic is an
attempt to smother the VB Classic community's source of oxygen. It may be harsh,
but it has a certain efficient effectiveness - if you're ruthlessly hard-hearted
enough to carry through - sort of like Auschwitz.

¤ > ¤ I'm not denying that there are alternative solutions. The problem with
¤ > the
¤ > ¤ alternative solutions is that they would bankrupt our company. That is
¤ > NOT a
¤ > ¤ solution.
¤ >
¤ > So if making the change from GoSub to Subs/Functions would bankrupt your
¤ > company then it sounds like
¤ > you should just leave the code as it is.
¤
¤ Ignorance is bliss. As if the only problem were the GoSubs, how about the
¤ control arrays? How about all of the other hundreds of things that make it
¤ impossible to port the code?
¤

I'm the one who is apparently ignorant. Why ask me?

We're NOT /asking/ you, senseless one, we're striving in vain to make you see
the truth - but you don't /want/ to see it, so our efforts are useless.

¤ > ¤ > Isn't one of
¤ > ¤ > the responsibilities of a programmer to develop alternative solutions
¤ > when
¤ > ¤ > a change to the platform
¤ > ¤ > or language occurs?
¤ > ¤
¤ > ¤ My job is to develop solutions to my clients' problems. It would have
¤ > been
¤ > ¤ nice if that was MS's job too.
¤ > ¤
¤ >
¤ > They do but apparently that *is* the problem for some.
¤
¤ Paul, if I were the only one complaining, you could smile smugly in your
¤ confidence. But I am just one of many of MS's clients that are not at all
¤ happy about what they have done.
¤

I wasn't completely happy with learning new object models either. Especially the data access
libraries that seem to change every three to five years. Those changes require almost *complete*
code rewrites.

So, the new object models just couldn't have been bolted onto VB Classic,
leaving existing code the way it was? Hmmm....ADO comes to mind.

But guess what? I decided to move forward because the alternative is obsolescence.

But things didn't /have/ to be that way, had Microsoft chosen otherwise.
Microsoft has been governed for a long time mainly by the precept of backwards
compatibility. Now that precept has been violated and they feign surprise that
it would have any impact on their customers.

<snip />

¤ > I'm not sure why you're focusing on one factor, as other's have, when I've
¤ > mentioned at least two or
¤ > three.
¤ >
¤ > ¤ > Sounds like it will be hurting for a long time until you decide to
¤ > address
¤ > ¤ > it. In addition, if you
¤ > ¤ > are continuing to use GoSub in new code then you have little to
¤ > complain
¤ > ¤ > about.
¤ > ¤
¤ > ¤ If addressing it means bankrupting my company, yes it will be a very
¤ > long
¤ > ¤ time. My guess is that it will be the same for others in the same boat.
¤ >
¤ > I'm sorry but I can't believe that the basis for the survival of your
¤ > company is dependent upon
¤ > GoSub.
¤
¤ The basis for the survival of our company is taking our code into the
¤ future. That seems to be at the bottom of Microsoft's agenda.

You have me convinced that it's at the bottom of yours as well.

No, he doesn't have to convince you. He is testifying of his position, something
he is uniquely in a position to know. You ought to take any man's testimony at
face value unless you have reason to believe otherwise - and apply common sense
tests to it. The fact that you ~refuse~ to do so, reveals your hopelessly
closed-minded bias.

How many different people must answer you before you *get a clue*? Check the
headers and look at our different posting histories - we are not the same person
posting with different personas, we are distinct individuals with radically
different histories and perspectives that somehow have come to a common
conclusion - based on an apparently obvious truth. You may choose to refuse to
discern the truth, but even a blind man knows that the rocks at the bottom of
the cliff won't feel any better for having refused to acknowledge or perceive
them.
_______________________
Michael B. Johnson
.

Relevant Pages

  • Re: VB6, VB2005, or Something Else?
    ... By the way, the preformance of Gosub in PCode was quite good, it ... ¤ ... I'm not complaining about the necessary changes, ... that Microsoft intentionally and unnecessarily made it more difficult. ...
    (microsoft.public.vb.general.discussion)
  • Re: Rolling the dice on vb6
    ... Stefan Berglund wrote: ... ¤ Yep, long gone. ... Let us say that Microsoft could write a real VB6 -> Fred ... MS could have had their business, could have had my business, and they ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... It seems to me that you are a proponent for the .net framework, ... Relating to the above 4 items: A small company selling software such as us ... Relating to the above 4 items: Can't Microsoft: ... ¤>we are. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤ Duh! ... Microsoft MVP ... GoSub is a bit dated - but no reason to kill it. ... possibly understand how a compiler or platform might work. ...
    (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)