Re: Visual Basic 6.0 support
- From: "Saga" <antiSpam@xxxxxxxxxxxxx>
- Date: Tue, 28 Jun 2005 13:22:05 -0500
Yeah, I saw your remarks in the thread started by Huw
"Microsoft Refuses to Answer..." but they did not seem
anything like he describes:
"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."
So I figured it was some other Dan, but 1) He gives no
reference as to what thread he is referencing. 2) Who this
"Dan" is or even what he is talking about! Just another
JAFO who can't follow up on the same thread...
Best regards,
Saga
"Dan Barclay" <Dan@xxxxxxxx> wrote in message
news:ejpXqC6eFHA.256@xxxxxxxxxxxxxxxxxxxxxxx
>
> "Saga" <antiSpam@xxxxxxxxxxxxx> wrote in message
> news:epXK97MeFHA.796@xxxxxxxxxxxxxxxxxxxxxxx
>>
>> Dan? Dan who? Are you referencing another thread?
>> If so, please indicate which, thank you.
>
> Heh. Dunno, but I'm a Dan. I missed the message you quoted so pardon
> me if I reply to the quoted portion of this one.
>
>>
>> Saga
>>
>> "Bryan Utley" <bryanutley2000NON@xxxxxxxxxxxxxxx> 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.
>
> My wife is still here, but come to think of it my dog is missing! Ya
> think? Naaaa...
>
>>> 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.
>
> Likewise. What's more, I've made a pretty good living at it and own
> my own company. FWIW, how you view MS's handling of the Basic
> language depends a whole lot on your point of view. If you *own* the
> code you write you don't appreciate the fact that you can't move it
> forward without rewriting.
>
> If you work for someone else who owns all the code you may or may not
> not "get it". To some folks, it's just an opportunity to do more
> programming (well, programming "again" what's already been done).
>
> As for leading the complaints, some of us have been out front on that
> just as we have been out front recognizing the improvements and
> promoting capabilities in the product in the past.
>
> What's more, we've been recognized for helping others with VB for
> years. I was in the first group of VB MVP's when they started the
> program in 1993 and was involved with Basic support long before that.
> Others you see complaining have been similarly involved. If you think
> I don't have the right to complain as strongly as I supported it,
> sorry you lose.
>
>>> 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.
>
> Yes, I've lobbied for that power as well. As an MVP I lobbied inside
> and outside. That's certainly not something I'd object to. FWIW,
> I've been a long time Basic cheerleader (long before Basic was made
> cool by VB).
>
> Interestingly, *none* of the great enhancements to the language proper
> folks talk about here required that MS break the existing language.
> They could all have been made through straightforward extension of the
> existing language. What's more, had the development team (or some
> other significant product team within MS) been users of the langauge
> that's exactly what would have happened.
>
>>> 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.
>
> Your older applications aren't worth moving forward? How quaint!
>
>>> And as for Dan, I am sure that he is still crying and bashing
>>> Microsoft
>>> that they no longer support Logo or QBasic.
>
> LOL.
>
>>> 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.
>
> I probably would feel much the same way if I hadn't been promised that
> they "got it" after the last major break in the language (VB4). At
> that time I agreed to back off, but I also told them that I wouldn't
> back off if they did it again. So, here we are.
>
> Several of us were brought to Redmond for the specific purpose of
> reviewing VB5 plans and to convince us that MS viewed VB as a real
> development langauge.
>
> Real development languages require, as a part of the langauge
> maintenance, that they do everything they can to preserve existing
> code *while* adding functionality. I, among most others there, were
> utterly convinced by what we saw that they intended to do just that.
>
> Unfortunately, they changed so many people on the team that the
> "institutional memory" was lost. There is no standard, nor is there a
> deprecation process. The "keeper of the keys" simply disappeared so
> the "new guys" felt like they had a clean slate.
>
>>> If I do not like a television program I simply change the channel
>>> until
>>> that program is finished.
>
> Yea, sorry I missed the original message here and have to respond to a
> quoted reply. That's mostly because I don't spend as much time here
> as I once did. You can usually find me over in the Delphi groups
> though.
>
>>> Just because ABC or NBC aires a bad program I
>>> don't boycott the network.
>
> That depends on how they go about it. FWIW, as a long time
> "cheerleader" I've convinced a lot of people to use VB. That was a
> mistake on my part. Folks considering that these days need to
> understand what they're getting into. VB.Net is a great language but
> VB has a history of being changed and, based on how it's managed
> internally, there is no doubt that will continue. ClassicVB is dead
> since it will not be updated and code written for it will not move
> forward to VB.Net.
>
>>> I think Microsoft has the most refined and polished tools for
>>> development at this time, so I use them.
>
> "Refined and polished" is great if you're just a programmer. If
> you're an application owner you really need to be thinking more long
> term.
>
>>> Bryan Utley
>
> I don't know who this Bryan guy is, or what he does for a living, but
> he really need to think long term. There are programmers and then
> there are developers.
>
>>> I have been programming for 23 years as a profession beginning with
>>> Cobol and CICS.
>
> Some folks have 23 years experience, others have 1 year 23 times.
>
> Good luck with your new code. You're gonna need it.
>
> Dan
>
>
.
- Follow-Ups:
- Re: Visual Basic 6.0 support
- From: Dan Barclay
- Re: Visual Basic 6.0 support
- References:
- Visual Basic 6.0 support
- From: Bryan Utley
- Re: Visual Basic 6.0 support
- From: Saga
- Re: Visual Basic 6.0 support
- From: Dan Barclay
- Visual Basic 6.0 support
- Prev by Date: Re: RaiseEvent from an item to collection
- Next by Date: Re: RaiseEvent from an item to collection
- Previous by thread: Re: Visual Basic 6.0 support
- Next by thread: Re: Visual Basic 6.0 support
- Index(es):
Relevant Pages
|
