Celebrity Deathmatch (VB.NET vs C#)
-
Oh sorry, it's so well known that I didn't think you'd need code to back it up :-) See this blog post: http://blog.gadodia.net/extension-methods-in-vbnet-and-c/[^]
Regards, Nish
Are you addicted to CP? If so, check this out: The Code Project Forum Analyzer : Find out how much of a life you don't have! My technology blog: voidnish.wordpress.com
You are right, it does not support passing the primary variable by reference. However, the other parameters can be passed by reference (this is what I thought you were initially claiming could not be done). One could workaround that by passing the primary variable through a second parameter by reference. Still, that's not as nice as VB.NET's implementation.
-
AspDotNetDev wrote:
C# Is Less Verbose
Not really. Like all C-based languages, C# requires symbols that are of no use either to compiler or humans who read the code. In the example above, the meaning of
SubandEnd Subis far clearer than{and}. That kind of "verbosity" is good. Truly expressive languages are for instance ones from ML family. Still too much syntax, but much cleaner and much less unneeded symbols than C/C++/Java/C#Perhaps I should have said "C# Is More Concise". :rolleyes: But kudos to you for bringing up the counter point that VB.NET is more expressive. I think, however, that it's expressive in areas which do not require expressiveness. Maybe "End Sub" makes the code easier to read to somebody not initiated with the language, but it doesn't make the code any easier to write (you would have to know the "End Sub" in advance, so it's not expressing anything until you write it yourself). Of course, intellisense adds "End Whatever" for you, which brings me to my counter point: If-Statements Are Easier To Type in C# Supposing you have a code block and you want to surround it with an if-statement. In VB.NET, you must type "End If" in full:
If True Then
' Code Block.If you press ENTER after "Then", the "End If" will be added in the wrong place. Instead, you can go to the bottom of the code block and type "End If". In C#:
if (true)
{
// Code Block.All you have to type is "}" and the code auto-indents nicely. Along those same lines, C# waits until you type the closing brace... VB.NET is a little eager and indents the code before you need it to.
-
Perhaps I should have said "C# Is More Concise". :rolleyes: But kudos to you for bringing up the counter point that VB.NET is more expressive. I think, however, that it's expressive in areas which do not require expressiveness. Maybe "End Sub" makes the code easier to read to somebody not initiated with the language, but it doesn't make the code any easier to write (you would have to know the "End Sub" in advance, so it's not expressing anything until you write it yourself). Of course, intellisense adds "End Whatever" for you, which brings me to my counter point: If-Statements Are Easier To Type in C# Supposing you have a code block and you want to surround it with an if-statement. In VB.NET, you must type "End If" in full:
If True Then
' Code Block.If you press ENTER after "Then", the "End If" will be added in the wrong place. Instead, you can go to the bottom of the code block and type "End If". In C#:
if (true)
{
// Code Block.All you have to type is "}" and the code auto-indents nicely. Along those same lines, C# waits until you type the closing brace... VB.NET is a little eager and indents the code before you need it to.
AspDotNetDev wrote:
VB.NET is a little eager and indents the code before you need it to.
Seems more like an IDE quirk than a language quirk...
Reminiscing just isn't what it used to be!! If you like cars, check out the Booger Mobile blog | If you feel generous - make a donation to Camp Quality!!
-
AspDotNetDev wrote:
VB.NET is a little eager and indents the code before you need it to.
Seems more like an IDE quirk than a language quirk...
Reminiscing just isn't what it used to be!! If you like cars, check out the Booger Mobile blog | If you feel generous - make a donation to Camp Quality!!
Indeed. Visual Studio has VB.NET Quirks [see above] Better? :rolleyes:
-
The VB Select-Case is more flexible than just that. Example from MSDN:
Dim number As Integer = 8
Select Case number
Case 1 To 5
Debug.WriteLine("Between 1 and 5, inclusive")
' The following is the only Case clause that evaluates to True.
Case 6, 7, 8
Debug.WriteLine("Between 6 and 8, inclusive")
Case 9 To 10
Debug.WriteLine("Equal to 9 or 10")
Case Else
Debug.WriteLine("Not between 1 and 10, inclusive")
End SelectRegards, Nish
Are you addicted to CP? If so, check this out: The Code Project Forum Analyzer : Find out how much of a life you don't have! My technology blog: voidnish.wordpress.com
I do like that about VB.NET. That would be nice if they added it to C#.
-
Perhaps I should have said "C# Is More Concise". :rolleyes: But kudos to you for bringing up the counter point that VB.NET is more expressive. I think, however, that it's expressive in areas which do not require expressiveness. Maybe "End Sub" makes the code easier to read to somebody not initiated with the language, but it doesn't make the code any easier to write (you would have to know the "End Sub" in advance, so it's not expressing anything until you write it yourself). Of course, intellisense adds "End Whatever" for you, which brings me to my counter point: If-Statements Are Easier To Type in C# Supposing you have a code block and you want to surround it with an if-statement. In VB.NET, you must type "End If" in full:
If True Then
' Code Block.If you press ENTER after "Then", the "End If" will be added in the wrong place. Instead, you can go to the bottom of the code block and type "End If". In C#:
if (true)
{
// Code Block.All you have to type is "}" and the code auto-indents nicely. Along those same lines, C# waits until you type the closing brace... VB.NET is a little eager and indents the code before you need it to.
AspDotNetDev wrote:
Maybe "End Sub" makes the code easier to read to somebody not initiated with the language, but it doesn't make the code any easier to write
Which is a reasonable trade-off. You write code once and read it many times. Besides, with any decent editor, it is a non-issue.
AspDotNetDev wrote:
if (true)
{I see unnecessary and confusing symbols here. For instance in Go, it would be something like:
if true {
Or (even better) in ML:
if true then
-
AspDotNetDev wrote:
Maybe "End Sub" makes the code easier to read to somebody not initiated with the language, but it doesn't make the code any easier to write
Which is a reasonable trade-off. You write code once and read it many times. Besides, with any decent editor, it is a non-issue.
AspDotNetDev wrote:
if (true)
{I see unnecessary and confusing symbols here. For instance in Go, it would be something like:
if true {
Or (even better) in ML:
if true then
Nemanja Trifunovic wrote:
You write code once and read it many times.
By that same reasoning, you learn a language once (well, can take a while for things to sink in) and you can develop software for many years based on that knowledge. It is faster to read "{}" than "Then End If", so why not go for the faster version since it is the one that will lead to the least overall time spent reading if-statements?
-
Indeed. Visual Studio has VB.NET Quirks [see above] Better? :rolleyes:
AspDotNetDev wrote:
Visual Studio has VB.NET Quirks
Oh, Zarquon, no... VS' VB editor keeps deleting stuff; I have to be very careful when I do certain things. I'd give a example, but the wife says that dinner is ready.
-
i'm not a vb guy anymore but when i was i LOVED exit on first failed step. ( instead of nested if's )
Select Case False Case Step1() Case Step2() Case Step3() End Selectcant do that in C#
Much like C, but C# semi-fixed that little problem. C# also doesn't have macroes like C, but VB has to continue to support them.
-
There hasn't been a good "why language X sucks and language Y is better" thread in a good while, so I thought I'd start one. Unlike most, however, this one has rules. I will post a reason C# is better than VB.NET and somebody reply with a reason VB.NET is better than C#. I (or somebody else) will then reply to that message stating another reason C# is better. And so on. Also, you must show code examples (when appropriate). I'll start. C# Is Less Verbose
Public Sub Something()
' VB.NET...
End Subpublic void Something()
{
// C#...
}You're turn (post why VB.NET is better than C#). :)
VB has
IsNot. -
AspDotNetDev wrote:
Visual Studio has VB.NET Quirks
Oh, Zarquon, no... VS' VB editor keeps deleting stuff; I have to be very careful when I do certain things. I'd give a example, but the wife says that dinner is ready.
PIEBALDconsult wrote:
I'd give a example, but the wife says that dinner is ready.
Yeah, I'd come up with some better examples, but I've been at work a couple hours past leaving time already.
-
VB has
IsNot. -
Perhaps I should have said "C# Is More Concise". :rolleyes: But kudos to you for bringing up the counter point that VB.NET is more expressive. I think, however, that it's expressive in areas which do not require expressiveness. Maybe "End Sub" makes the code easier to read to somebody not initiated with the language, but it doesn't make the code any easier to write (you would have to know the "End Sub" in advance, so it's not expressing anything until you write it yourself). Of course, intellisense adds "End Whatever" for you, which brings me to my counter point: If-Statements Are Easier To Type in C# Supposing you have a code block and you want to surround it with an if-statement. In VB.NET, you must type "End If" in full:
If True Then
' Code Block.If you press ENTER after "Then", the "End If" will be added in the wrong place. Instead, you can go to the bottom of the code block and type "End If". In C#:
if (true)
{
// Code Block.All you have to type is "}" and the code auto-indents nicely. Along those same lines, C# waits until you type the closing brace... VB.NET is a little eager and indents the code before you need it to.
AspDotNetDev wrote:
If you press ENTER after "Then", the "End If" will be added in the wrong place. Instead, you can go to the bottom of the code block and type "End If". In C#:
That is an intellinonsense/Editor feature NOT a language feature.
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
-
AspDotNetDev wrote:
If you press ENTER after "Then", the "End If" will be added in the wrong place. Instead, you can go to the bottom of the code block and type "End If". In C#:
That is an intellinonsense/Editor feature NOT a language feature.
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
Well, part if it is an intellisense/editor feature. The whole having to type "End If" is part of the language though. And I'm not excluding things that are due to the editor. A clever enough editor would allow me to type in C# and convert it to VB.NET as I type... and it would apply a filter so that I would see C# when the underlying code is VB.NET. :rolleyes:
-
Nemanja Trifunovic wrote:
You write code once and read it many times.
By that same reasoning, you learn a language once (well, can take a while for things to sink in) and you can develop software for many years based on that knowledge. It is faster to read "{}" than "Then End If", so why not go for the faster version since it is the one that will lead to the least overall time spent reading if-statements?
Yeah, the "C way" is better. It's much more flexible. See here for an example.[^] Also, several times I have changed an
ifto awhile-- in VB you have to change both ends. X| Plus, using more symbols and fewer keywords makes C somewhat less Anglo-centric.modified on Monday, March 28, 2011 11:52 PM
-
Yeah, the "C way" is better. It's much more flexible. See here for an example.[^] Also, several times I have changed an
ifto awhile-- in VB you have to change both ends. X| Plus, using more symbols and fewer keywords makes C somewhat less Anglo-centric.modified on Monday, March 28, 2011 11:52 PM
PIEBALDconsult wrote:
in VB to have to change both ends
I forgot about that! I ran into that today, actually. The most annoying one for me is "Function"/"Sub". Why the heck should I have to annotate that difference? They're both methods. Let the bloody compiler figure out if it returns something or not. I find it strange that VB.NET doesn't have "Begin Grouping" and "End Grouping" rather than parentheses. :rolleyes:
PIEBALDconsult wrote:
Plus, using more symbols and fewer keywords makes C somewhat less Anglo-centric.
Good point!
-
Which ain't the same thing.
-
Which ain't the same thing.
IsToo... IsNot... rofl... :laugh:
Reminiscing just isn't what it used to be!! If you like cars, check out the Booger Mobile blog | If you feel generous - make a donation to Camp Quality!!
-
Nemanja Trifunovic wrote:
You write code once and read it many times.
By that same reasoning, you learn a language once (well, can take a while for things to sink in) and you can develop software for many years based on that knowledge. It is faster to read "{}" than "Then End If", so why not go for the faster version since it is the one that will lead to the least overall time spent reading if-statements?
AspDotNetDev wrote:
It is faster to read "{}" than "Then End If",
Kind of.
End Ifcloses the block afterIfand that's it. To get what}does you need to be aware of the scope - sometimes even to scroll up a couple of pages. Sure, a good editor helps, but as far as a language goes I likeEnd Ifbetter. -
Yeah, the "C way" is better. It's much more flexible. See here for an example.[^] Also, several times I have changed an
ifto awhile-- in VB you have to change both ends. X| Plus, using more symbols and fewer keywords makes C somewhat less Anglo-centric.modified on Monday, March 28, 2011 11:52 PM
PIEBALDconsult wrote:
Would you double-check that link? I saw nothing related to your arguments there (using Chrome 10 on Fedora Linux).
PIEBALDconsult wrote:
Plus, using more symbols and fewer keywords makes C somewhat less Anglo-centric.
Meh, as a Cyrillic-writing Serbian I'll take Anglo-centric any time over cryptic symbols. In fact, my ideal language would have no operators at all - not even mathematical ones.