Visual Basic Yesterday, Today and Tomorrow

A month or two ago, Paul Yuknewicz and I sat down to record a Hansselminutes podcast with Scott Hanselman, talking about the past, present and future of Visual Basic. It was a lot of fun, check it out!

Also, here’s a little holiday love for VB from some Microsofties you might recognize:

10 thoughts on “Visual Basic Yesterday, Today and Tomorrow

  1. sandeep j

    yesterday vb 6.0 it was too good

    today it is drastically changed so as to learn it from scrach, it’s too complicated to learn and to work with now

    Tomorrow is again hope for some way to get our old vb back with just control improvements and new controls

    Reply
  2. George

    Where can I get 64-bit ocx vb controls? I installed VS 2008 Pro (licensed copy). Could not find any 64-bit OCXs.

    Thanks very much.

    George

    Reply
  3. Gordon

    Speaking of yesterday, I recall using Basic on a HP85 back in the years 1980-1985.

    More recently, I have used VBA for the last 10 years, compiling to COM and running under Microsoft Excel.

    There is no comparison in my mind. The HP product was the best by a mile.

    Sorry bout that!

    Reply
  4. Billy Hollis

    Wha????? Do we have some sarcasm going on in the comments? Kernel drivers? 1980 HP Basic being superior? For what, writing to a character-based screen? Old VB coming back?

    Sorry, guys, I just don’t get where you’re coming from here.

    Reply
  5. Csaba

    Hi,

    For intance, creating a scientific graph was just so simple with HP85: on the screen, plotter or printed. What has VB and .net compared with that? Already the HP9830 computer from the 70-ties could simply create scientific graphs on a plotter. (And, yes HP9830 just had a single line LED display – not even a CRT)

    Yes, HP85 and HP9830 had imaginary numbers – just imagine that! Eveyrthing has NOT improved the last 30 years of "personal computing"! Just remember, Simula 67 is from 1967!

    Further, it was just so simple to control external instruments with the HP documentation, regardless if which 9800 HP workstation it was. You just read the documentation and then programmed! No courses needed, no helpdesk needed, no question via Internet needed! .net is NOWWHERE close when it comes to that documentation, not even if you buy 5-10 books about VB programming.

    But yes VB2005 has a number of advantages that the old HP "Rocky Mountain" Basic and HP Pascal lacked. Yes, WinForms and WPF is much better for fancy meningless games for boys of all ages and sexes but it is useless to present scientific data! Unless you wrte you own modules/classes.

    Then we have the stability issue. Do anyone of you remember a time when a control and measurement program was reliable "because it was controlled by a computer". Now that is more or less a joke!

    Happy new year!

    Csaba

    Reply
  6. David

    My hope for the future of VB is that we actually get Visual Basic back. What’s being delievered now is not Visual Basic. It’s some other language that is slower to develop in and slower to execute.

    I look forward to the day VB7 is released. Take VB6, fix the few minor bugs, make it work properly on Vista and ship it.

    Reply
  7. Ulu

    Don’t listen to these guys! Who said VB is for scientific graphs? Yes, if you want it, just take one of a hundred available libraries and make your graph in any color, any resolution, in a sec.

    Controlling external devices from a workstation :))))

    VB.Net is the best.

    One thing is sad, however. Why do we are always one or two features behind C#? I mean, stuff like the My namespace are great (which is not a part of the language but an IDE feature), but I missed the anonymous delegates a lot, and here we are, VB9, we have lambdas but only Functions, not Subs, and Subs are much helpful sometimes (e.g., if you need an even handler). Same thing with iterators and other minor stuff.

    Anyway, it feels like VB is more for applications, while C# is for component development. This is one of the reasons why the "serious" programmers frown upon VB. Hopefully this thing changes when VB becomes more dynamic.

    ulu

    Reply
  8. Russ Yeagley

    I’ve been a developer since 1980. In 1989, I went to a symposium in Chicago, where I met Tom Button from Microsoft. He mentioned about a new flavor of BASIC that I might be interested in. (Yeah, they still used caps to spell BASIC then.) To make a long story short, I began kicking the tires on Project Thunder (VB 1.0) not too long afterwards. I also betaed VB 2 & 3, later on. Sure I also coded in Pascal, C and Assembler, but VB has always had a special place in my professional career. I am very happy to see where Visual Basic has come, and I’m also happy to think about where it’s probably going. I’m saddened by some of the prejudice that is still rearing it’s ugly head about VB, but who cares. After all, there are a whole bunch of us who know what really can be done using VB!

    Reply

Leave a Reply