Re: to Ken Halter and the other dedicated VB MVPs

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

From: MM (kylix_is_at_yahoo.co.uk)
Date: 01/23/05


Date: Sun, 23 Jan 2005 16:49:10 +0000

On Tue, 18 Jan 2005 19:26:33 GMT, "smith"
<rcsTAKEOUT@smithvoiceTAKEOUT.com> wrote:

>The intense off-topic VB6/VB.Net thread "Where is the Key in Treeview.Net"
>(started Dec 2 2004 and cross-posted to every VB group under the sun) really
>got me to thinking.
>
>And that thinking got me to typing this:
>
>http://www.smithvoice.com/C1swf.htm
>
>All the best in 2005 and here's hoping that this year's Visual Basic release
>will be more to the VB core's liking.
>
>Robert Smith
>Kirkland, WA
>www.smithvoice.com

I read that article of yours (http://www.smithvoice.com/C1swf.htm) and
I am reassured that old, real VB-ers simply refuse to crawl away and
die! There is one problem with VB.Net. It isn't Visual Basic! Sure,
call it C# with BASIC-like syntax if you wish, but it bears as much
comparison to VB6 and earlier versions that my late gran ever did to
Julia Roberts (well, they were both women, I suppose).

Good to hear that there are new products like Flash and Actionscript.
Over here in "old" Europe we use Flash to clean the floors, but if it
works on Windows, too, then maybe I'll take a look. I did just click
on the link "if current releases are any indicator" and was shunted on
to a Microsoft web site, where, after interminable churning of my
modem for a few minutes, it just said "Flash 7 Not Detected" or some
such, at which point I thought, Bill Gates is still in charge, then.
Then I left. (I usually treat Microsoft with contempt. Sorry, it's the
way I'm made.)

As for giving VB what VB-ers allegedly said they needed, what they got
was worse than a hole in the head. Where *were* all the folks crying
out for OOP in a quick-n-dirty RAD program generator? Only a very
small proportion from the three million-odd VB programmers, going on
what I was reading at the time. Countless MVPs themselves criticised
VB.Net and said that Microsoft was completely on the wrong track. And
then Microsoft delivered a product that hardly anyone had a good word
to say about, and it seems, even after three or more years, still
don't.

I still fire up my trusty VB6 occasionally, like going out into the
yard and kicking the tyres on an old Fordson tractor. VB6 still works
fine. One day, someone with more foresight than Bill Gates, Stevie
"Developers" Ballmer, and several others put together will produce a
new state-of-the-art simple RAD to rival real Visual Basic, i.e. the
one prior to VB.Net, and the world will beat a path to that
innovator's door. Meanwhile, OOP fanatics will just have to see how
far they can get on Microsoft's managed platforms with 100 meg
downloads.

MM



Relevant Pages

  • Re: Microsoft not content with "dissing" just the Classic VB Developer Army....
    ... I've read the petition and I can't ... Microsoft can satisfy the "issues" in the petition (which pretty much boil ... Nothing but adding unmanaged VB6 into the VS.NET IDE ... COM interop support, a poor code conversion wizard, the ending of mainstream ...
    (microsoft.public.dotnet.languages.vb)
  • Re: EXE Erstellen
    ... Denn dass die MSDN-Versionen von VB6, ob auf CD/DVD oder per Subscription b/gezogen, unter eine persönliche Lizenz fallen, ist ja auch nicht neu. ... M.E. wird da ein Popanz aufgezogen - und es wird wieder einmal versucht, die Nachbesserung unternehmerischer Fehler Microsoft unterzuschieben. ... Software ist von beiden Phänomenen nicht betroffen. ... Im Falle des Rechtsstreits um die Einbindung von Objekten wären wahrscheinlich zahlreiche andere Hersteller ebenfalls betroffen. ...
    (microsoft.public.de.german.entwickler.dotnet.vb)
  • Re: Why to use VBA?
    ... Please don call me selfish for not counting VB; YES MS did lose some VB developers that were unwilling to port to new platform BUT the number of office customers is not comparable to VB 6! ... The fact is that VB.NET is sufficiently incompatible with the previous version of VB (VB6, from which VBA is derived) that for all practical purposes an upgrade wasn't possible, you had to rewrite the code more or less from scratch. ... The automated code converters provided by Microsoft were next to useless, and the fact that Microsoft went and changed lots of names of objects and properties meant that late-binding code wouldn't work without rewrite because it couldn't be automatically converted at all. ...
    (microsoft.public.word.vba.general)
  • Re: Please do NOT sign the VB.COM petition
    ... I think that the proposed solution is one of the cheapest possible solutions which will please the VB6 community. ... I know some dozens of people who signed the petition, and only /very few/ of them believe the suggested way is the only way. ... However, I don't think this is a good idea, because it costs Microsoft money without bringing money back to Microsoft. ... All of those other teams are taking lots of resources from the .NET Framework and VB.NET teams. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Why to use VBA?
    ... The fact is that VB.NET is sufficiently incompatible with the previous version of VB (VB6, from which VBA is derived) that for all practical purposes an upgrade wasn't possible, you had to rewrite the code more or less from scratch. ... The automated code converters provided by Microsoft were next to useless, and the fact that Microsoft went and changed lots of names of objects and properties meant that late-binding code wouldn't work without rewrite because it couldn't be automatically converted at all. ... Lots of people asked Microsoft what that reason was, with regard to that and dozens of other changes to the language. ...
    (microsoft.public.word.vba.general)