someone can tell me if delphi is better to visual basic ?

define better

It's always hard to define 'better' in these questions. First, I'm assuming you're talking about Delphi vs. VB, and not VB.Net. In the .Net arena they are both fairly similar. In fact, one of the cheif architects of .Net was the original developer of the Delphi system.

I think you will find Delphi to be much more component-rich than VB. The array of whats included right of the bat is staggering. For my money, Delphi is also a better IDE over all than the Visual Studio product line (IMHO).

I'm a big C/C++ fan, and I used VC++ for many years (even wrote a book on it). Delphi uses the Pascal language which takes some getting used to, though you can use C++ Builder and use that same rich component set.

Delphi has a version for Linux named Kylix, that is supposed to allow you to port your Windows program to Linux with little fuss as long as you write well-behaved code. I've never actually done this though.

Delphi's pascal is object-oriented (VB really isn't, VB.Net is) which is always good.

In terms of speed, very very few people will notice any difference, and I'm sure that each one will excel in their own areas. Truth is most programs these days spend most of their time waiting for database queries or internet connections than executing our code.

As an IDE and language, I think Delphi with Pascak is better, though I'm not big Pascal fan. But you'll find more jobs and oppurtunities with VB and Microsoft products (Borland is a bit oddball doing things like changing their name to Inprise and then back to Borland).

When I have to write a program (either for myself or for pay), 99% I choose Delphi.

I have the same question before. Which is better vb.net or csharp? Until i tried both and finally decided vb.net is much better because it's much easier.

in my opinion, there is not better between VB and Delphi.
If you're more happy with Pascal syntax, select Delphi.
If you're more happy with Basic syntax, select VB.

everything be done in delphi can be done in VB and reverse!

While I agree that anything you can do in with 1 you can do with the other, I find Delphi incredibly easier than VB. Compared to VB.Net things are closer.

The Delphi components make it a real RAD tool. You can lay out a complex UI with splitters, child windows, resizers etc with practically zero lines of code.

Of course, at some point all those windows and buttons need actual code behind them, and at that point the two start to act similar.

Whenever I give a demonstration of the Delpi IDE (to programming students) they are always blown away by the simplicity of the initial layout.

The best way I can describe the IDE is that it is intuitive and works the way you would think it should.

As to what you feel comfortable with, I would bet the person asking feels equally comfortable with both, and would further guess that they are just starting out in either. That of course, is just an assumption.

It's always hard to define 'better' in these questions. First, I'm assuming you're talking about Delphi vs. VB, and not VB.Net. In the .Net arena they are both fairly similar. In fact, one of the cheif architects of .Net was the original developer of the Delphi system.

I think you will find Delphi to be much more component-rich than VB. The array of whats included right of the bat is staggering. For my money, Delphi is also a better IDE over all than the Visual Studio product line (IMHO).

I'm a big C/C++ fan, and I used VC++ for many years (even wrote a book on it). Delphi uses the Pascal language which takes some getting used to, though you can use C++ Builder and use that same rich component set.

Delphi has a version for Linux named Kylix, that is supposed to allow you to port your Windows program to Linux with little fuss as long as you write well-behaved code. I've never actually done this though.

Delphi's pascal is object-oriented (VB really isn't, VB.Net is) which is always good.

In terms of speed, very very few people will notice any difference, and I'm sure that each one will excel in their own areas. Truth is most programs these days spend most of their time waiting for database queries or internet connections than executing our code.

As an IDE and language, I think Delphi with Pascak is better, though I'm not big Pascal fan. But you'll find more jobs and oppurtunities with VB and Microsoft products (Borland is a bit oddball doing things like changing their name to Inprise and then back to Borland).

When I have to write a program (either for myself or for pay), 99% I choose Delphi.

http://en.wikipedia.org/wiki/Anders_Hejlsberg

Anders Hejlsberg is the perrson behind C# and .Net.

VB have OOP, it's just not the purist's way but lanauages like C++ and VB are all heading toward the OOP way, what is OOP? VB have it, it just called Module.

http://discuss.joelonsoftware.com/default.asp?joel.3.397928.31

the OOP concept already there, the lanagues (VB) itself just wasn't really desgin for the purist OOP until the VB.net but the concept/idea of OOP is there. Remeber the outcry of VB6 developers about MS making major changed to VB due to the fact that people said VB have no OOP. the OOP concept is there but it take a major redesgin to make it more pure OOP but then you get bunch of people mad at you because you break away from the tradition. i guess you really can't win if you're MS. too much security then AV companies like Synmatec and McAfee will cry about it and too little security will make your users mad at you.

i for one welcome the new changes in VB but then again, if you are going to program in .Net, C# might be the better choice.

Yes, Anders Hejlsberg is the person behind C# and .Net. And if you read your own Wiki reference, it also mentions Delphi.

As to VB (not VB.Net) having OOP characteristics, I respectfully disagree. It's true you can create re-usable code in modules, but that is not OOP. There is no inheritance, no polymorphism, constructors, or destructors implemented at a syntax level (please note: 'Syntax level'). OOP languages, in my opinion, merely implement a syntax to make simpler something that good programmers have done for years before OOP became a buzzword. At times, C with function pointers in structures looks and acts a lot like C++ member functions. But the truth is that an OOP language implements the good programming approach as a an automatic part of the language, and not as extra code the developer must write. According to your definition where any module ability is OOP, then all languages are OOP, including Assembly.

And speaking of Assembly, consider this: Any language, OOP or not, breaks down to machine instructions or byte code. There is no 'magic' generated by an OOP language. All an OOP language really does is make code reuse and extendability easier at a syntax level. It doesn't instantly make a program better (if bad programmers can write spaghetti code with non-OOP languages, I guess they can also create meatball objects with an OOP language).

You might consider me a purist, but I think I'm just being careful with my words. I'm not saying VB is bad, or that you can't write good reusable code with it. I'm merely saying it isn't an OOP language. A soda can isn't a coffee cup, even if I put coffee in it. Both can hold liquid, but one is simply better at holding hot coffee.

Yes, Anders Hejlsberg is the person behind C# and .Net. And if you read your own Wiki reference, it also mentions Delphi.

As to VB (not VB.Net) having OOP characteristics, I respectfully disagree. It's true you can create re-usable code in modules, but that is not OOP. There is no inheritance, no polymorphism, constructors, or destructors implemented at a syntax level (please note: 'Syntax level'). OOP languages, in my opinion, merely implement a syntax to make simpler something that good programmers have done for years before OOP became a buzzword. At times, C with function pointers in structures looks and acts a lot like C++ member functions. But the truth is that an OOP language implements the good programming approach as a an automatic part of the language, and not as extra code the developer must write. According to your definition where any module ability is OOP, then all languages are OOP, including Assembly.

And speaking of Assembly, consider this: Any language, OOP or not, breaks down to machine instructions or byte code. There is no 'magic' generated by an OOP language. All an OOP language really does is make code reuse and extendability easier at a syntax level. It doesn't instantly make a program better (if bad programmers can write spaghetti code with non-OOP languages, I guess they can also create meatball objects with an OOP language).

You might consider me a purist, but I think I'm just being careful with my words. I'm not saying VB is bad, or that you can't write good reusable code with it. I'm merely saying it isn't an OOP language. A soda can isn't a coffee cup, even if I put coffee in it. Both can hold liquid, but one is simply better at holding hot coffee.


well, consider VB is much older with root in Basic. it got a lot of leftover from older version in order to stay backward comptiable and that is hard to move it toward more modern lanauge.

yeah, i do consider you as purist but that's ok since the funk and soul of VB wasn't really in OOP or other concept. it is the ability of RAD (Rapid application development) to quickly develop a Windows/Web(ASP/ASP.net) application that make VB popular thus its own downfall or maybe not if you look at it from different point of view.

RAD is really the soul of VB.

To let the topic digress even further....

VB has it's roots in Basic, which was created in 1964. Delphi has it's roots in Pascal, which was begun in 1968. VB came out about '91, and Delphi about '95. Both products where amazing in their day, and quickly improved in their next version (though VB3 and VB6 offered the most improvements). Both Delphi and VB have what could be considered a bastardized version of their respective languages.

I do consider VB to be one of the first RAD tools. No argument there. I was blown away the first time I tried it. I just personally think that Delphi is better (and has been since it was released in '95). More intuitive, more components and classes, the ability to generate more statically-linked executables (how many times can you recall needing to put vbrun.dll on a desktop for distribution?), etc.

It's like a vintage motorcycle vs. a modern sports bike. That vintage bike might look romantic and be nostalgic, but drum brakes and kick-starts kinda get tired fast. Though if anyone had a Vincent Black Shadow, I'ld stand in line for it.

Personally, I make a living writing code in a mixture of Delphi (majority) for Windows desktops and sometimes MSVC++, C/C++ for Palm and MobileWindows devices, and ColdFusion and PHP for web servers (No Java or .Net worth mentioning). I don't care what language I use, because I like the activity of coding itself, and it's nice to try different languages. So I put the 'Funk and Soul' in the creative process, not in the language.

I think Delphi is over-all better, and VB is overall more commonly accepted.

vb.net (not the old vb6) and c# are both oO and compile to the same code the only difference is cosmetic in the syntax. vb.net is basic style. c# is java/c style. choosing between the two is really a matter of personal taste. c# is less verbose and very similar to java which is why i use it.

vb.net

IF 1=1 THEN
'do this
END IF

c#

if (1==1) {
// do this
}

same thing just different syntax.

I think, VB is easier than delphi, so from this side it is better =)

I always worked with Delphi and tryed VB.net the other day it looks practically the same you just need to learn that some syntax are different in both.