redfiretruck

Hey... I was wondering which was better... Vb or C#? In reliability/Speed hopefully .

I mean, as far as actually possiblities/speed/controls... Which is better VB or C# and more importantly... Why is C# special/unique and what is good about it? Just wondering .

Narue

>I was wondering which was better... Vb or C#?
That depends. Which do you like better?

>as far as actually possiblities/speed/controls... Which is better VB or C#
They're pretty much identical in all of the categories you mentioned, excluding programmer quality. If you suck as a programmer, you can write crap code in any language.

>Why is C# special/unique and what is good about it?
It sounds like you've already made your decision, but I'll bite. Ultimately, the difference is what kind of programmer the language is meant to draw from other languages. For example, C# would draw programmers with a C, C++, or Java background and VB.NET would draw VB6 programmers.

__________________
Even if the voices aren't real, they have some pretty good ideas.

lectricpharaoh

What Narue said. In a nutshell, professional programmers who are familiar with C, C++, and/or Java will be more inclined to use C# over VB.NET. Amateur programmers who are somewhat familiar with legacy VB (ie, VB before .NET) will likewise be more inclined to use VB.NET. This is the main reason that VB.NET has a poorer reputation than C#.

That said, though, both languages are functionally identical in almost every respect. They both compile down to the same IL, or intermediate language, which is what all of the .NET languages compile to. That coupled with the fact that the bulk of your program is likely to be composed of .NET classes and controls, which are common between .NET languages, means that notwithstanding programmer skill, a program won't be more efficient in one language than another.

__________________
And once again, Probability proves itself willing to sneak into a back alley and service Drama as would a copper-piece harlot.
- Vaarsuvius, Order of the Stick

redfiretruck

Ahh, well the main reason I ask is because with delphi while using a repeat function it goes so fast it practically locks the computer up most the time. But VB's repeat code (whether it is because of speed or not) only slows down the form and doesn't even use that much power.

Since C# has so many delphi/C like codes and stuff, i figured they were most likely similar in speed and stuff with delphi or C (which pwns the crap out of VB)

As far as actually liking C#, it is a bit of a wierd thing... I mean... I like that i add the ";" at the end of the line (just because I'm so used to habit that i usually have to delete them from VB).

What i don't like about C#? The text is all caps-sensitive, and the buttons are all named confusingly (i mean, if it's cap-sensitive i would like it to be all lower case. Name changing is too much work imo xD). More importantly though, with VB i have a bro who sometimes programs with it and he can help me out from time to time .

I mean don't get me wrong, C# is cool and all and is practically but it just isn't what i personally like .

Jabo

The case-sensitive part is a lot like Java. Does C# enforce classes like Java?

Narue

>Does C# enforce classes like Java?
Yes.

>Since C# has so many delphi/C like codes and stuff, i figured they
>were most likely similar in speed and stuff with delphi or C
Don't judge the speed of a language by it's appearance. C# and VB.NET use the same framework, and ultimately they're really the same language: MSIL. As such, they have the same performance characteristics.

>The text is all caps-sensitive
Oddly enough, the de facto standard for VB.NET is to capitalize the first letter of each word, so while VB.NET is case-insensitive, you're still somewhat expected to follow the common casing conventions. Personally, I think the case argument against C# is full of hot air because of that.

C# is definitely more strict though, but in my opinion that breeds better code by making the programmer think.

__________________
Even if the voices aren't real, they have some pretty good ideas.

Alias

You would be mistaken to think that identical MSIL code is generated, yes they both boil down to MSIL, but MSIL, like any other language, can approach problems in a number of different ways. Basically, two methods (a VB.NET version and a C# version) of functionally the same substance, and using the same types exposed via .NET assemblies could and alot of the time would compile into maybe similar MSIL, but certainly not 'the same' MSIL code.

Also, something that is unique about C# is that is was designed specifically for utilising the .NET Framework and in certain instances elements of the .NET Framework were written with that in mind, hence we get a language and framework that essentially work 'best' as a team in comparison to the other available languages.

Narue

>You would be mistaken to think that identical MSIL code is generated
Yes, that would be a mistake, as the VB.NET and C# compilers are written by different teams. Please point out where I said the same code would be generated.

__________________
Even if the voices aren't real, they have some pretty good ideas.

Alias

Sorry Narue, I did not mean to aim my post as being a direct response to your own and instead inteded to provide an angle from which the OP could look from that had not already been approached.

BstrucT

C# is Case sensitive, definetlely. That's why I like to use intellisense!
Although I have to say that the intellisense feature can definetely speed up some coding purposes, but I also play with Sharpdevelop to ensure I don't grow too lazy with syntax!



>BstrucT

__________________
The more the human race tries to change everything, when not needed, the less will they be able to change themselves when they need to.