Visual Basic, Visual Basic vs. Visual C++

Visual Basic vs. Visual C++

Author	Message
David Butto #1 / 9	Visual Basic vs. Visual C++ We are undertaking a new project with a relatively agressive time frame and we're trying to decide whether to program in Visual Basic or Visual C++. It is a desktop application which will typically be running on 486's with 4M-8M of memory. We are primarily concerned with the speed of the application (both actual and perceived), availability of competent programmers, and the time to develop (we are under a rather aggressive time schedule). If anyone has read any helpful publications or has performed/seen some benchmark applications, please respond to this message. Any help you can give will be greatly appreciated. Thanks, David Button
Mon, 15 Jun 1998 03:00:00 GMT

Jens Balchen J #2 / 9	Visual Basic vs. Visual C++ Quote: >We are undertaking a new project with a relatively agressive time >frame and we're trying to decide whether to program in Visual Basic or >Visual C++. It is a desktop application which will typically be running >on 486's with 4M-8M of memory. We are primarily concerned with the speed >of the application (both actual and perceived), availability of competent >programmers, and the time to develop (we are under a rather aggressive >time schedule). If anyone has read any helpful publications or has >performed/seen some benchmark applications, please respond to this >message. This topic must be as old as the mountains.... Anyway, two (not always correct) rules: o VC's executable is always faster than VB's o VB's development time is always faster than VC's Jens -- * Everything I said are the opinions of someone else. * * I just cut-and-pasted. * Jens Balchen jr. http://www.sn.no/~balchen
Mon, 15 Jun 1998 03:00:00 GMT

Myakl #3 / 9	Visual Basic vs. Visual C++ Quote: >We are undertaking a new project with a relatively agressive time >frame and we're trying to decide whether to program in Visual Basic or >Visual C++. Why decide? I use a mix of both in most all projects, even throw in Access for some devlopmen time tools. I do not see them as mutually exclusive. - Mike
Tue, 16 Jun 1998 03:00:00 GMT

Myakl #4 / 9	Visual Basic vs. Visual C++ writes: Quote: >This topic must be as old as the mountains.... I remember long ago the arguments RAGED in the same way on C vs Pascal. Pascalites contended that it was superior because it complied faster and did not need to be linked. Only the names have changed...... - Mike
Tue, 16 Jun 1998 03:00:00 GMT

YComputi #5 / 9	Visual Basic vs. Visual C++ Quote: >>We are undertaking a new project with a relatively agressive time >>frame and we're trying to decide whether to program in Visual Basic or >>Visual C++. >Why decide? I use a mix of both in most all projects, even throw in >Access for some devlopmen time tools. >I do not see them as mutually exclusive. Ahhhh! Please do your eventual replacement a favor and don't do this! How many people out there are really good at Visual C++, Visual Basic AND Access? Visual C++ is fine for writing DLL's for VB where speed is critical, but make sure that the C++ code will never need to be maintained if you go this route. If you start mixing and matching, you sacrifice the #1 need in business software -- maintainability. Especially if you have an aggressive time-frame, stick exclusively with VB. Yes, you can go faster with VC++ (I've written code in both to demonstrate this), but VB isn't slow enough to warrant the maintenance hassle of dragging in C++. Steve Young Young Computing
Tue, 16 Jun 1998 03:00:00 GMT

Myakl #6 / 9	Visual Basic vs. Visual C++ Quote: (YComputing) writes: >>>We are undertaking a new project with a relatively agressive time >>>frame and we're trying to decide whether to program in Visual Basic or >>>Visual C++. >>Why decide? I use a mix of both in most all projects, even throw in >>Access for some devlopmen time tools. >>I do not see them as mutually exclusive. >Ahhhh! Please do your eventual replacement a favor and don't do this! >How many people out there are really good at Visual C++, Visual Basic AND >Access? If they are trying to DECIDE between VB and VC there MUST be a (percieved anyway) expertise availabloe in both. As for Access, Jeez, it is built for Dilbert's boss to run - surely a development team can handle using it for what it is good for, Quote: >Visual C++ is fine for writing DLL's for VB where speed is critical, but >make sure that the C++ code will never need to be maintained if you go >this route. Infinitely doable. There is another advantage though: Common code procs across a development team - wrap 'em up in a DLL to minimize changes, duplicated code and application size. Quote: >If you start mixing and matching, you sacrifice the #1 need in business >software -- maintainability. I agree with the later clause, but not the first. The act of adding some C procs to a support DLL, or hiding essentials like a security kernel or trade secret algorithms in a DLL does not negatively impact maintainability. It CAN but, again, since they are deciding betwixt VB and VC, I am assuming some C expertise. I would not council that they LEARN VC just to do mixed language development, but MS has made it so easy to leverage the best of C, the best of VB, the best of Office, it is kinda there to take advantage of, provided the expertise is there. Quote: >Especially if you have an aggressive time-frame, stick exclusively with >VB. Yes, you can go faster with VC++ (I've written code in both to >demonstrate this), but VB isn't slow enough to warrant the maintenance >hassle of dragging in C++. By that reasoning we should rule out OLE servers, API calls and third party tools. Quote: >Steve Young >Young Computing Sorry, No $ale M Yaklin ProTools Development Systems
Wed, 17 Jun 1998 03:00:00 GMT

John M. Mia #7 / 9	Visual Basic vs. Visual C++ Quote: >We are undertaking a new project with a relatively agressive time >frame and we're trying to decide whether to program in Visual Basic or >Visual C++. It is a desktop application which will typically be running >on 486's with 4M-8M of memory. We are primarily concerned with the speed >of the application (both actual and perceived), availability of competent >programmers, and the time to develop (we are under a rather aggressive >time schedule). If anyone has read any helpful publications or has >performed/seen some benchmark applications, please respond to this >message. Any help you can give will be greatly appreciated. If you are tring to decided between C++ and VB then the tool you really should be using is Delphi (AKA Borland Pascal). Delphi has the visual development environment of VB and is a compiled language that has move of the OO capabilities of C++. Delphi is compiled so it speed is comperable to C++ (i.e. a lot faster than VB.) If you are under a tight schedule then using C++ on Windoze is not the thing to be doing. I have been doing C++ programing for 8 years but have given up doing it under the mess that is called MS Windows. John ------------------------------------------------------------ OVERTHROW THE AMERICAN LEGAL SYSTEM -- DON'T SERVE ON JURIES Use any excuse to get out. Tell them you advocate {filter} overthrow of the government...whatever it takes. If we can stop them from getting jurors then we can do to the lawyers what they've been doing to us. The American Legal System: Of the lawyers, by the lawyers, for the lawyers ------------------------------------------------
Wed, 17 Jun 1998 03:00:00 GMT

A Cameron Mitche #8 / 9	Visual Basic vs. Visual C++ : We are undertaking a new project with a relatively agressive time : frame and we're trying to decide whether to program in Visual Basic or : Visual C++. It is a desktop application which will typically be running : on 486's with 4M-8M of memory. We are primarily concerned with the speed : of the application (both actual and perceived), availability of competent : programmers, and the time to develop (we are under a rather aggressive : time schedule). If anyone has read any helpful publications or has : performed/seen some benchmark applications, please respond to this : message. Any help you can give will be greatly appreciated. : Thanks, : David Button David, You need more memory. My opinion is that the best of all possible worlds is to use VB for interface (display and input) and C to do serious things in the form of .dll. Cameron
Thu, 18 Jun 1998 03:00:00 GMT

jd #9 / 9	Visual Basic vs. Visual C++ Quote: >>>We are undertaking a new project with a relatively agressive time >>>frame and we're trying to decide whether to program in Visual Basic or >>>Visual C++. >>Why decide? I use a mix of both in most all projects, even throw in >>Access for some devlopmen time tools. >>I do not see them as mutually exclusive. >Ahhhh! Please do your eventual replacement a favor and don't do this! >How many people out there are really good at Visual C++, Visual Basic AND >Access? I am. If you are keeping a count.
Thu, 18 Jun 1998 03:00:00 GMT

Page 1 of 1

[ 9 post ]