If you had to move from VB6...
in [Visual Basic]
|
Prev: Ever had to judge a new to-be-hired in interview ? REPOST
Next: Multiple Combo Boxes Highlighted - Solved
From: bitshifter on 15 Feb 2010 10:33 In another thread, someone said that compared to VB Fred, VB6 was pathetic. This low attempt to turn me from my private choice of language slid off my back like water on a duck. However, it did pique my curiosity. If I had to move from VB6, which language would I choose. Which language would most resemble it in IDE, ease of coding and, yes, RAD quality. I would accept a learning curve about the same I had to go through with VB6. About a hundred hours to get a simple database program running (from picking up the course book) and about a year or two to get moderatly proficient in it. I came up with RealBasic, Delphi (though I heard it's on the way out), maybe C# (but I would try to keep away from M$ stuff), and not Java. What do you think ?
From: sloan on 15 Feb 2010 10:56 VB.NET is easiest pick. VB.NET is not VB(classic). HOWEVER, I have found benefit from making a "clean break", and instead of accidentally bringing any bad vb6 practices with you, going to C# is my suggestion. 2 reasons. Reason 1 is that most msdn code samples are in vb.net and c#. So your famaliarity with vb will make seeing the C# sample "pop out" to you, because you'll usually have the vb.net sitting right above it. Reason 2 is that most microsoft internal development is done in C# now. If you've ever attending TechEd or any other Microsoft event, you are hard pressed to find any vb.net example in the presentations. Check this: http://www.codeproject.com/KB/dotnet/CSharpVersusVB.aspx Do I agree 100% of it, maybe not. However it is a good read to do as you make YOUR decision on what to do. Criticism's of the article are fine (from other posters). But picking one point and saying "that's stupid, disregard the entire article" is the ole throw the baby out with the bath water. I think the article above is a good read to ~~assist you in making your decision, but not to make the decision for you. Good luck. It's 2010. It's time to move forward. But VS2010/C# would be my suggestion (among the many different ones you might receive). VS2010 is only a few weeks off. Its in RC mode right now ( Release Candidate ) which you can get from technet.microsoft.com <bitshifter(a)sympatico.ca> wrote in message news:4b79674f.1840625(a)news.newshosting.com... > In another thread, someone said that compared to VB Fred, VB6 was > pathetic. > > This low attempt to turn me from my private choice of language slid > off my back like water on a duck. > > However, it did pique my curiosity. > > If I had to move from VB6, which language would I choose. > Which language would most resemble it in IDE, ease of coding and, yes, > RAD quality. > > I would accept a learning curve about the same I had to go through > with VB6. About a hundred hours to get a simple database program > running (from picking up the course book) and about a year or two to > get moderatly proficient in it. > > I came up with RealBasic, Delphi (though I heard it's on the way out), > maybe C# (but I would try to keep away from M$ stuff), and not Java. > > What do you think ?
From: Jeff Johnson on 15 Feb 2010 11:10 <bitshifter(a)sympatico.ca> wrote in message news:4b79674f.1840625(a)news.newshosting.com... > If I had to move from VB6, which language would I choose. > Which language would most resemble it in IDE, ease of coding and, yes, > RAD quality. Not so much what I WOULD do but what I DID do was to move to C#. But then I already had experience with C before VB, so it wasn't that much of a shock to me.
From: Tom Shelton on 15 Feb 2010 11:30 On 2010-02-15, bitshifter(a)sympatico.ca <bitshifter(a)sympatico.ca> wrote: > In another thread, someone said that compared to VB Fred, VB6 was > pathetic. > Just so you understand - I in no way meant that VB6 overall was pathetic. I was only making reference to the particular features that were called out in the post I responded to... > This low attempt to turn me from my private choice of language slid > off my back like water on a duck. > > However, it did pique my curiosity. > > If I had to move from VB6, which language would I choose. > Which language would most resemble it in IDE, ease of coding and, yes, > RAD quality. > > I would accept a learning curve about the same I had to go through > with VB6. About a hundred hours to get a simple database program > running (from picking up the course book) and about a year or two to > get moderatly proficient in it. > > I came up with RealBasic, Delphi (though I heard it's on the way out), > maybe C# (but I would try to keep away from M$ stuff), and not Java. > > What do you think ? Well personally, I moved years ago to C#. But, if I was going non-MS, I would go Java or C++. If I wanted to stay with basic (unlikely), then I would look at powerbasic. -- Tom Shelton
From: mayayana on 15 Feb 2010 11:36
> > I came up with RealBasic, Delphi (though I heard it's on the way out), > maybe C# (but I would try to keep away from M$ stuff), and not Java. > Why maybe C# and not Java? C# was designed to compete with Java. They're both semi-sandboxed, OO, JIT-compiled systems running on a VM and designed for server-side/intranet applets. Isn't the question, really, whether you want to go along with a sandboxed OS -- Microsoft's planned future of software as a service? Maybe a future where you might shortly have to buy webhosting on Azure and get approval in order for your software to run on Windows? One can be for or against that, but it seems important to go into it with eyes open. .Nxt is the Java-fying of the Windows API. It's a radical new direction. There have been several discussions of various 3rd-party Basics here in the past. I can never keep track of them all, and most (including the Linux-based attempts) seem to have the fatal flaw that they see all Basic coders as glorified scripters who need everything encased in safe wrappers. They equate verbose code with stupidity. (What I like to think of as "Perl syndrome". :) I think Nobody posted a comprehensive list at one point. Maybe he'll share that again. |