how to choose among VC/VB/C#?
-
QUESTION 1: how to choose between VB.NET/C#/VC.NET? With all due respect, VB.NET seems to have it all: a. better code samples and documentation... too many examples: DMO/ADO/... I wouldnt want to waste time with C++ trying to figure out some API that couldnt have been so easy to program if proper documentation is available (and in many cases, such docs is available, but to VB and C# only)! b. speed - not slower than VC.NET isnt it (since all compile to IL)? c. best dialog editor d. ease of use (and now it's multithreaded + object oriented) e. most likely to attract a large user base? VC seems like an obsolete tool. well, a low level dev tool perhaps (where u want to create buffer overflow). And VB.NET seems like to be the tool that get the job done and done fast. QUESTION 2: according to code project and code guru forums membership statistics, it seems VC6 is still a much more popular/dominant development tool. but perhaps this is because codeguru and codeproject are both C++ sites? QUESTION 3: any good sites for VB/VB.NET forums? downloads/tutorials? What do u think? Correct me if i'm wrong since I do wish to pick the right tool for future development projects. norm
-
QUESTION 1: how to choose between VB.NET/C#/VC.NET? With all due respect, VB.NET seems to have it all: a. better code samples and documentation... too many examples: DMO/ADO/... I wouldnt want to waste time with C++ trying to figure out some API that couldnt have been so easy to program if proper documentation is available (and in many cases, such docs is available, but to VB and C# only)! b. speed - not slower than VC.NET isnt it (since all compile to IL)? c. best dialog editor d. ease of use (and now it's multithreaded + object oriented) e. most likely to attract a large user base? VC seems like an obsolete tool. well, a low level dev tool perhaps (where u want to create buffer overflow). And VB.NET seems like to be the tool that get the job done and done fast. QUESTION 2: according to code project and code guru forums membership statistics, it seems VC6 is still a much more popular/dominant development tool. but perhaps this is because codeguru and codeproject are both C++ sites? QUESTION 3: any good sites for VB/VB.NET forums? downloads/tutorials? What do u think? Correct me if i'm wrong since I do wish to pick the right tool for future development projects. norm
norm wrote: With all due respect, VB.NET seems to have it all: b. speed - not slower than VC.NET isnt it (since all compile to IL)? c. best dialog editor d. ease of use (and now it's multithreaded + object oriented) e. most likely to attract a large user base? b C# is as quick c. C# uses the same dialog editor d. C# does all that with a decent syntax to boot e. C# will attract all comers, where VB is for IT Journalists and managers. f. C# is designed for .NET, where VB is bodged for backwards compatability Michael Fat bottomed girls You make the rockin' world go round -- Queen
-
QUESTION 1: how to choose between VB.NET/C#/VC.NET? With all due respect, VB.NET seems to have it all: a. better code samples and documentation... too many examples: DMO/ADO/... I wouldnt want to waste time with C++ trying to figure out some API that couldnt have been so easy to program if proper documentation is available (and in many cases, such docs is available, but to VB and C# only)! b. speed - not slower than VC.NET isnt it (since all compile to IL)? c. best dialog editor d. ease of use (and now it's multithreaded + object oriented) e. most likely to attract a large user base? VC seems like an obsolete tool. well, a low level dev tool perhaps (where u want to create buffer overflow). And VB.NET seems like to be the tool that get the job done and done fast. QUESTION 2: according to code project and code guru forums membership statistics, it seems VC6 is still a much more popular/dominant development tool. but perhaps this is because codeguru and codeproject are both C++ sites? QUESTION 3: any good sites for VB/VB.NET forums? downloads/tutorials? What do u think? Correct me if i'm wrong since I do wish to pick the right tool for future development projects. norm
norm wrote: With all due respect, VB.NET seems to have it all: LOL - yeah, that's it...... norm wrote: better code samples and documentation Ya. You see, C++ programmers are smart enough to convert from VB samples to C++ on the fly, so often things are only documented in VB. norm wrote: speed - not slower than VC.NET isnt it (since all compile to IL)? Wrong - C++ IL is actually optimised. Microsoft made a big deal of this to try and get C++ programmers to subject their code to an intermediate runtime. norm wrote: best dialog editor I'll give you this, although I'm told only until Feb. norm wrote: ease of use (and now it's multithreaded + object oriented) This is subjective. I am using VB at work and I think it's a pig of a thing. norm wrote: most likely to attract a large user base? Not a chance in hell. C# is where the action is. norm wrote: VC seems like an obsolete tool. :omg::laugh: norm wrote: well, a low level dev tool perhaps (where u want to create buffer overflow). Well, just because you've never had to be smart enough to manage any memory does not mean a C++ program, properly written, should have a chance in hell of having a buffer overflow. None of my code has or will ever suffer from this problem. You're thinking of C. norm wrote: And VB.NET seems like to be the tool that get the job done and done fast. Getting the job done fast, and barely adequately, has always been VB's claim to fame. But why do you think we have C# ? Because even if VB ever turns into a real programming language ( and with .NET it's probably close, seeing as they all target the same IL ), the name of VB is beyond repair, it has been associated with too many crappy hack programmers writing too much bad code for too long. C# will replace VB within a couple of years. Already C# has a fair bit over VB.NET ( I know you read that thread, so I won't link to it ), and with more to come, Microsoft are trying to channel both real programmers, and VB heads into using C#. norm wrote: according to code project and code guru forums membership statistics, it seems VC6 is still a much more popular/dominant development tool. but perhaps this is because codeguru and codeproject are both C++ sites
-
norm wrote: With all due respect, VB.NET seems to have it all: b. speed - not slower than VC.NET isnt it (since all compile to IL)? c. best dialog editor d. ease of use (and now it's multithreaded + object oriented) e. most likely to attract a large user base? b C# is as quick c. C# uses the same dialog editor d. C# does all that with a decent syntax to boot e. C# will attract all comers, where VB is for IT Journalists and managers. f. C# is designed for .NET, where VB is bodged for backwards compatability Michael Fat bottomed girls You make the rockin' world go round -- Queen
Slow down with the great VB quotes already !!!! :P Christian No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002 C# will attract all comers, where VB is for IT Journalists and managers - Michael P Butler 05-12-2002 Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002
-
norm wrote: With all due respect, VB.NET seems to have it all: LOL - yeah, that's it...... norm wrote: better code samples and documentation Ya. You see, C++ programmers are smart enough to convert from VB samples to C++ on the fly, so often things are only documented in VB. norm wrote: speed - not slower than VC.NET isnt it (since all compile to IL)? Wrong - C++ IL is actually optimised. Microsoft made a big deal of this to try and get C++ programmers to subject their code to an intermediate runtime. norm wrote: best dialog editor I'll give you this, although I'm told only until Feb. norm wrote: ease of use (and now it's multithreaded + object oriented) This is subjective. I am using VB at work and I think it's a pig of a thing. norm wrote: most likely to attract a large user base? Not a chance in hell. C# is where the action is. norm wrote: VC seems like an obsolete tool. :omg::laugh: norm wrote: well, a low level dev tool perhaps (where u want to create buffer overflow). Well, just because you've never had to be smart enough to manage any memory does not mean a C++ program, properly written, should have a chance in hell of having a buffer overflow. None of my code has or will ever suffer from this problem. You're thinking of C. norm wrote: And VB.NET seems like to be the tool that get the job done and done fast. Getting the job done fast, and barely adequately, has always been VB's claim to fame. But why do you think we have C# ? Because even if VB ever turns into a real programming language ( and with .NET it's probably close, seeing as they all target the same IL ), the name of VB is beyond repair, it has been associated with too many crappy hack programmers writing too much bad code for too long. C# will replace VB within a couple of years. Already C# has a fair bit over VB.NET ( I know you read that thread, so I won't link to it ), and with more to come, Microsoft are trying to channel both real programmers, and VB heads into using C#. norm wrote: according to code project and code guru forums membership statistics, it seems VC6 is still a much more popular/dominant development tool. but perhaps this is because codeguru and codeproject are both C++ sites
-
QUESTION 1: how to choose between VB.NET/C#/VC.NET? With all due respect, VB.NET seems to have it all: a. better code samples and documentation... too many examples: DMO/ADO/... I wouldnt want to waste time with C++ trying to figure out some API that couldnt have been so easy to program if proper documentation is available (and in many cases, such docs is available, but to VB and C# only)! b. speed - not slower than VC.NET isnt it (since all compile to IL)? c. best dialog editor d. ease of use (and now it's multithreaded + object oriented) e. most likely to attract a large user base? VC seems like an obsolete tool. well, a low level dev tool perhaps (where u want to create buffer overflow). And VB.NET seems like to be the tool that get the job done and done fast. QUESTION 2: according to code project and code guru forums membership statistics, it seems VC6 is still a much more popular/dominant development tool. but perhaps this is because codeguru and codeproject are both C++ sites? QUESTION 3: any good sites for VB/VB.NET forums? downloads/tutorials? What do u think? Correct me if i'm wrong since I do wish to pick the right tool for future development projects. norm
norm wrote: a. better code samples and documentation... I have noticed this too. Allthough I honestly don't spend alot of time looking for code examples of things done in C++, I just don't see the amount of examples that I do for VB. norm wrote: b. speed - not slower than VC.NET isnt it (since all compile to IL)? Again, I have to go by experiance here. I ran some tests way back using VB6 and VC6 and VC was faster at most things. However, when I looked at the differences in speed for what I was using it for VS. the knowledge that I already had vested in VB6, VB won hands down. I was not writing timing critical code, nor was a writing anything that HAD to be done tight. When I DID have an occasion to do something time critical I wrote a DLL and called it from VB. I have not done any comparisons in .NET between the two, but I stil belive that VC will be a bit (albeit maybe not too much) fatser than VB.NET/C# norm wrote: c. best dialog editor Hands down here I think you are right. I have not seen Everrett (sp) but I think this has been one of the things that have made VB and C# a very attractive language for most developers. I hate using VC resources to design dialog boxes, and MFC always seemed like a PITA to me. I like being able to address a text boxes text by using TextBox1.Text. norm wrote: d. ease of use (and now it's multithreaded + object oriented) I am a firm lover of VB (so I have to admit that I AM Biased here). VB finally got the shot of steriods that it neded to compete with the other languages. norm wrote: e. most likely to attract a large user base? I really disagree with this one though. I think in the long run C# will be the langauge of choice for most new developers. I ahev to admit that VB seems like it was only included in .NET because of the years of legacy code that is already in place for alot of companies. Allthough I still firmly belive that VB is a first class language, I can see the handwriting on the wall that says that things are progressing and that C# is the way to go from now on. Does that mean that I am dropping VB all together? NOPE, not on your life. But new things that are intended to be wround for the long term will be done in C#. Hope this helps.
Paul Watson wrote: "At the end of the day it is what you produce that counts, not how many doctorates you have on t
-
"I'll give you this, although I'm told only until Feb." > what? in feb we'll get a dialog editor for VC? norm
I believe that is part of the next version, yes. Christian No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002 C# will attract all comers, where VB is for IT Journalists and managers - Michael P Butler 05-12-2002 Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002
-
I believe that is part of the next version, yes. Christian No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002 C# will attract all comers, where VB is for IT Journalists and managers - Michael P Butler 05-12-2002 Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002