Re: Visual Basic 6.0 support

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

While I'll not comment on the things people do and say about their
unhappiness at the lack of migration paths as I'm not of that wing to even
do anything, I will admit I do admit I harbour slight suspicions that there
are a minority of people/organisations that bitch because they want, rather
than need, a migration path....I get the impression that there are a lot of
VB6 applications being re-written in .NET unnecessarily, the excuse being
that "VB6 might not work on a future operating system" when really it's just
a case of a developer has something they're proud of, and wants to be in the
position where they've got all their such work in the most powerful,
evolving technology there is available - but they're ticked off because they
'have to' effectively repeat work (if they're going to accomplish that
position). I'm not saying that's a bad thing - I must say I myself have been
guilty of making the decision that .NET could "take something in a new
direction" when this decision hasn't been 100% based on commercial
cost-to-benefit effectiveness of the product.

So while I don't want to undermine genuine needs, I am curious to hear from
people who have a 'friend of a colleague' that is miffed that backward
compatibility left a big gap between VB6 and .NET, but are slightly more
miffed about the fact that it doesn't *actually* matter, because VB6 is
still 32 bit, the combined meaning being that they will have to go on using
VB6 with its lack of OO, for at least some of the time?

"Bryan Utley" <bryanutley2000@xxxxxxxxx> wrote in message
news:uSuLybFeFHA.616@xxxxxxxxxxxxxxxxxxxxxxx
>I am not sure who this Dan guy is or what he does for a living, but I
> don't think I have ever run across a man who acts like such a spoiled
> child. After reading his post, you would think Microsoft or Ballmer
> himself stole his his wife and raped his dog.
>
> I have been programming for 23 years as a profession beginning with
> Cobol and CICS. I was even using QBasic years ago and remember when
> VB-1 came out. People were all excited about the increased capabilities
> of the language. In addition, I have read forums about people bitching
> that VB-1/2/3/4/5 and now VB-6 could not do this or that and why
> Microsoft didn't give it most popular programming language the power
> and/or flexibility to access certain objects or capabilities of Windows.
>
> Now Microsoft has provided these same capabilities to VB that C/C++
> programmers have enjoyed for years. I moved to VB.net in 2002 and have
> not looked back one bit. When I find it necessary to update an older
> application, I simply fire up VB6 and go.
>
> And as for Dan, I am sure that he is still crying and bashing Microsoft
> that they no longer support Logo or QBasic. As with everything
> involving computers it is necessary to be dynamic and flexible, or we
> would all still be programming in MASM or interperter Basic using our
> brand new 8Mhz 8088 system from IBM.
>
> As far as I am concerned, sure I think it would be nice if Microsoft
> would come out with a VB-7 and 8 and so on, but that is simply not in
> the cards. I see no reason to bash Microsoft, I don't always agree with
> there decisions but I do not sit in on every meeting in Redmond and I do
> not listen to the request of hundreds of thousands of users like
> Microsoft employees do.
>
> If I do not like a television program I simply change the channel until
> that program is finished. Just because ABC or NBC aires a bad program I
> don't boycott the network.
>
> I think Microsoft has the most refined and polished tools for
> development at this time, so I use them.
>
> Bryan Utley
>
> *** Sent via Developersdex http://www.developersdex.com ***


.

Relevant Pages

  • Re: Visual Basic.net
    ... >>I think that in fairness to Microsoft and it's recent controversial ... VB6 is an old dog that should have been put down years ago. ... Nevertheless, typically a programming ... >language should /abstract/ from platforms and technologies and thus a change ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Visual Basic.net
    ... I think that in fairness to Microsoft and it's recent controversial ... VB6 is an old dog that should have been put down years ago. ... maintain a language entrenched in 1960's programming ideas for so long was ... Object oriented programming was invented in 1968 and even C++ was 15 years ...
    (microsoft.public.dotnet.languages.vb)
  • Re: .NET vs Java (Windows service development)
    ... you forget to often that persons who make a living of programming cannot do the things like you. ... Although there were also who asked even in 2008: "Do it with VB6 and then had the idea it was cheaper" Most of those are now probably screaming that Microsoft is stealing because it is now so expensive to emigrate and that it is the fault of Microsoft that VB6 is not anymore working on every new OS; while they were warned in fact already in 2002 for that. ... In this case it is a principal who says do it with Java. ...
    (microsoft.public.vb.general.discussion)
  • Re: Book suggestions VB .Net/Visual Studio 2005
    ... Nobody is suggesting that you should stay with VB6 for the rest of your life. ... It is a different product that just happens to be produced by the same company that produced VB6 and that has been dishonestly sprinkled with some "VB6 sounding language constructs" purely as a slick marketing trick. ... If you are looking for a replacement for VB6 then of course you should consider VB.Net, but you should consider it alongside all other programming environnments from manufacturer's other than Microsoft and make up your mind which is best suited to your needs, taking fully into account the fact that ALL of them, including VB.Net, will require you to port your code over to a different language and also taking into account the fact that Microsoft have shown themselves to be thoroughly untrustworthy. ... The same as what happens when any language, including Visual Studio 2005 and VB.Net, is no longer supported on the operating system or systems for which you are programming. ...
    (microsoft.public.vb.general.discussion)
  • Re: I must be dumb or something
    ... I think it's undeniable that with VB6 it was very easy to write a very bad ... It's a fact that there was an enormous number of low-skilled developers ... was at bringing programming to the masses, but it did introduce a problem ... and put a breakpoint there. ...
    (microsoft.public.dotnet.general)