VB6 vs. VB.NET

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • JzWild
    Registered User
    • May 2001
    • 6
    #1

    VB6 vs. VB.NET

    How many of you have played with the beta version of Visual Studio.NET? Thoughts? What are your thoughts on M$ deciding to include more backward compatability for VB6 than they originally planned.
    Will you be using .NET when it is released, or sticking to VB6, or both. Why?

    And what about C#?

    It looks to me like VB.NET is turning into a real language (and it looks like ASP+ KICKS ASS). What will the 90% of VB programmers who never used any of VB6's advanced features do now that they will have to know about inheritance and polymorphism? Stick with VB6, is my guess.




    [This message has been edited by JzWild (edited 05-19-2001).]
    Tags: None
    • wiZd0m
      Confirmed User
      • Feb 2001
      • 1526
      #2
      Last I check, You can't avoid the Objects very much in VB6 can you? Because everything is an Object

      Show me somethin that is not Object ...

      Ok, so now you answered your question.

      And if they don't they are not programmers...

      ------------------
      wiZd0m
      Fortune Pussy Adult Links
      ----------
      wiZd0m

        Comment

        • Jcman
          Registered User
          • May 2001
          • 27
          #3
          VB.NET is going to have real OO features? Please give details. I'm tired of every moron who can use VStudio macros to generate database "apps" calling himself a programmer.
          VB might become a real language if they added inheritance and real encapsulation. Is MS finally getting a clue?

            Comment

            • JzWild
              Registered User
              • May 2001
              • 6
              #4
              Originally posted by Jcman:
              VB.NET is going to have real OO features? Please give details. I'm tired of every moron who can use VStudio macros to generate database "apps" calling himself a programmer.
              VB might become a real language if they added inheritance and real encapsulation. Is MS finally getting a clue?
              Please explain why inheritance is so important. I use it in C++ every day but I don't think it's a really important feature. Inheritances more than one level deep are vanishingly useful.

              As for encapsulation, that's one of those ideas like reciprocity or empathy; one is either born with it or not. Programmers who don't see the wisdom of hiding implementation are people who should be, oh, serving hamburgers or washing bottles .. not writing code.

              VB actually did more for encapsulation than C++. C++ doesn't require developers to think, but anyone writing an OCX for VB found himself unable to use global variable or turn him implementation inside out and let clients hook up to its guts. These people were dragged kicking and screaming into writing halfway-partitioned code.


                Comment

                • Paul Markham
                  Too old to care
                  • Jun 2001
                  • 52942
                  #5
                  Lensman is a hypocrite


                  The Revive Juicybone Now Coalition



                  Blowout deal. 880 videos, 2,400 image sets, plus many RAW videos. $500.
                  PM me for a deal. Skype Paulmarkham70

                    Comment

                    Previous template Next
                    Working...