Re: Sorry to see you go VB6. Here's to the future...


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 4 of 4

Thread: Re: Sorry to see you go VB6. Here's to the future...

  1. #1
    Richard Curzon Guest

    Re: Sorry to see you go VB6. Here's to the future...

    > I do. It's a form of belittlement. Same as when Bill Storage, and
    others, come here
    > and label folks "whiners."
    >


    I admit to emotions about VB6 demise, how can I be calling Mike a whiner?!

    Let's have a subthread about the emotional impact of losing VB6, and just
    call it that!? Let's be "90's" men (and women, but that's culturally
    redundant, no <g>) ( Or is that a "naughties" men, you first Karl? )

    My own personal VB6 frameworks and addins are *finally* in a state I can be
    happy with, fully reusable, and now they are heading for the dustbin. I
    feel bad about the demise of VB6 in many, many ways. Outweighed in my case,
    but still.

    Most of us here could probably say VB6 was as near to a "calling in life" as
    anything we have, a mastery we've invested the best years of our lives for,
    an art we've become "gurus" in ( that probably covers most of us here, in
    SOME people's eyes <g> ).

    Mike wants no features of dotnet, no changes in VB6, just a 5 year promise
    "in stone". Which, noone has ever given in the history of the industry, of
    course. And which by demonstrated practice and experience is probably
    unnecessary (pointing to VB3 experience for example).

    Eliminate the logical, what's left is emotional. Sorry to see you go VB6,
    but there's life beyond...

    regards
    Richard.




  2. #2
    Karl E. Peterson Guest

    Re: Sorry to see you go VB6. Here's to the future...

    Hi Richard --

    > > I do. It's a form of belittlement. Same as when Bill Storage, and
    > > others, come here and label folks "whiners."

    >
    > I admit to emotions about VB6 demise, how can I be calling Mike a whiner?!


    Heh, well, I'll give ya Mike! Here, take him. Please. <g>

    > Let's have a subthread about the emotional impact of losing VB6, and just
    > call it that!? Let's be "90's" men (and women, but that's culturally
    > redundant, no <g>) ( Or is that a "naughties" men, you first Karl? )


    LOL

    > My own personal VB6 frameworks and addins are *finally* in a state I can be
    > happy with, fully reusable, and now they are heading for the dustbin. I
    > feel bad about the demise of VB6 in many, many ways. Outweighed in my case,
    > but still.
    >
    > Most of us here could probably say VB6 was as near to a "calling in life" as
    > anything we have, a mastery we've invested the best years of our lives for,
    > an art we've become "gurus" in ( that probably covers most of us here, in
    > SOME people's eyes <g> ).
    >
    > Mike wants no features of dotnet, no changes in VB6, just a 5 year promise
    > "in stone". Which, noone has ever given in the history of the industry, of
    > course. And which by demonstrated practice and experience is probably
    > unnecessary (pointing to VB3 experience for example).
    >
    > Eliminate the logical, what's left is emotional. Sorry to see you go VB6,
    > but there's life beyond...


    Have I got a t-shirt for you!

    Later... Karl
    --
    http://www.mvps.org/vb/rants/dotnotT.xxx.htm



  3. #3
    Joe \Nuke Me Xemu\ Foster Guest

    Re: Sorry to see you go VB6. Here's to the future...

    "Karl E. Peterson" <karl@mvps.org> wrote in message <news:3b54b964@news.devx.com>...

    > Hi Richard --


    > > My own personal VB6 frameworks and addins are *finally* in a state I can be
    > > happy with, fully reusable, and now they are heading for the dustbin. I
    > > feel bad about the demise of VB6 in many, many ways. Outweighed in my case,
    > > but still.


    Quit your whining and start rewriting, you trust-fund baby!

    > Have I got a t-shirt for you!
    >
    > Later... Karl
    > --
    > http://www.mvps.org/vb/rants/dotnotT.xxx.htm


    Put some especially nasty Migration Lizard output on the back! Or would
    this violate your EULAs and NDAs?

    --
    Joe Foster <mailto:jfoster@ricochet.net> On the cans? <http://www.xenu.net/>
    WARNING: I cannot be held responsible for the above They're coming to
    because my cats have apparently learned to type. take me away, ha ha!



  4. #4
    Mike Mitchell Guest

    Re: Sorry to see you go VB6. Here's to the future...

    On Tue, 17 Jul 2001 16:45:25 -0400, "Richard Curzon"
    <rcurzon@spamcop.net> wrote:

    >Mike wants no features of dotnet, no changes in VB6, just a 5 year promise
    >"in stone".


    I never said I would not welcome enhancements to VB6. I was fully
    expecting VB7 to turn up one day, as an incremental, evolutionary
    change from VB6, with new features, bug fixes to old ones, refinements
    to existing stuff (for instance, the improvement in control array
    handling between VB5 and VB6). I would even not complain too much
    about additions to the OOP facilities within a real VB7, as I was able
    to pick and mix my OOP contingent in VB6 and VB5.

    What I shall never cease of tiring to tell you, is that I don't want
    the fundamental paradigm shift as represented by VB.NET. I never, ever
    asked for anything as Draconian as this, and I am sure that those who
    *did* want inheritance and other OOP features never expected that
    their request would be interpreted so freely by Microsoft and thereby
    give the latter carte blanche to reinvent the wheel and turn 10 years
    of progressive improvement in RAD on its head.

    MM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center