March 22, 2012 at 11:33 am
patrickmcginnis59 (3/22/2012)
UnbalancedKarma (3/22/2012)
http://www.codeproject.com/Articles/10135/Not-Another-C-Versus-VB-Article?msg=3050761#xx3050761xxThe article is the usual C#/VB snobbery and in-fighting but the linked reply makes some good points in the case for VB.NET.
Comparing the two is always invitation for a massive flame-war, personally I don't think there's much in it (I use C#) although "on error resume next" in VB is a God-Tier feature.
From the article:
"80% of C# programmers are good, while 80% of VB programmers are not good."
I had better file that away for future reference. I can use it as a point of debate!
Whose definition of good?
March 22, 2012 at 12:06 pm
Lynn Pettis (3/22/2012)
patrickmcginnis59 (3/22/2012)
UnbalancedKarma (3/22/2012)
http://www.codeproject.com/Articles/10135/Not-Another-C-Versus-VB-Article?msg=3050761#xx3050761xxThe article is the usual C#/VB snobbery and in-fighting but the linked reply makes some good points in the case for VB.NET.
Comparing the two is always invitation for a massive flame-war, personally I don't think there's much in it (I use C#) although "on error resume next" in VB is a God-Tier feature.
From the article:
"80% of C# programmers are good, while 80% of VB programmers are not good."
I had better file that away for future reference. I can use it as a point of debate!
Whose definition of good?
Nigel Shaw the author of the article of course!
It must be correct because he used percentages!
March 22, 2012 at 12:08 pm
patrickmcginnis59 (3/22/2012)
Lynn Pettis (3/22/2012)
patrickmcginnis59 (3/22/2012)
UnbalancedKarma (3/22/2012)
http://www.codeproject.com/Articles/10135/Not-Another-C-Versus-VB-Article?msg=3050761#xx3050761xxThe article is the usual C#/VB snobbery and in-fighting but the linked reply makes some good points in the case for VB.NET.
Comparing the two is always invitation for a massive flame-war, personally I don't think there's much in it (I use C#) although "on error resume next" in VB is a God-Tier feature.
From the article:
"80% of C# programmers are good, while 80% of VB programmers are not good."
I had better file that away for future reference. I can use it as a point of debate!
Whose definition of good?
Nigel Shaw the author of the article of course!
It must be correct because he used percentages!
Yea, right. I have a bridge for sale, interested? 😉
March 22, 2012 at 1:45 pm
UnbalancedKarma (3/22/2012)
http://www.codeproject.com/Articles/10135/Not-Another-C-Versus-VB-Article?msg=3050761#xx3050761xxThe article is the usual C#/VB snobbery and in-fighting but the linked reply makes some good points in the case for VB.NET.
Comparing the two is always invitation for a massive flame-war, personally I don't think there's much in it (I use C#) although "on error resume next" in VB is a God-Tier feature.
I find the on error resume next to be one of the scariest and most misused features of any language. Most of the time I have seen it used it is to avoid having to do proper error handling. Instead of logging the error or informing the user/calling program of a problem it used to squelch the error. IMHO that is not error handling, it is error suppression which can be very dangerous.
The thought about resizing an array is ridiculous. I have not used a sized array since I was working in VB6. Even in .NET 1.1 an ArrayList was far superior to a fixed length array in so many ways (dynamic size with no redim preserve, sorting, finding, etc).
But you are 100% spot on that these discussions can quickly turn into a religious war. Oh wait didn't we just have one of those a couple days ago with Steve's editorial about tabs vs spaces???
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
March 22, 2012 at 3:49 pm
I have to admit I agree about the case sensitivity routine, but not for the reasons most people do. I don't care about having to type properly, that's not the concern.
The problem, for me, is when I'm trying to inherit things and some wiseacre decides to create a "name" object when a "Name" object exists and I have to go bounding through the code to determine which one is actually the one I wanted, and it's usually like 8 levels deep before I find the incredibly minor difference on some overloaded method.
"It's case sensitive, it's supposed to be able to do that!"
*Backhanded b!tchslap*
"Don't do that if you don't want the rest of us to drop you off a bridge."
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
March 22, 2012 at 6:27 pm
patrickmcginnis59 (3/22/2012)
Lynn Pettis (3/22/2012)
patrickmcginnis59 (3/22/2012)
UnbalancedKarma (3/22/2012)
http://www.codeproject.com/Articles/10135/Not-Another-C-Versus-VB-Article?msg=3050761#xx3050761xxThe article is the usual C#/VB snobbery and in-fighting but the linked reply makes some good points in the case for VB.NET.
Comparing the two is always invitation for a massive flame-war, personally I don't think there's much in it (I use C#) although "on error resume next" in VB is a God-Tier feature.
From the article:
"80% of C# programmers are good, while 80% of VB programmers are not good."
I had better file that away for future reference. I can use it as a point of debate!
Whose definition of good?
Nigel Shaw the author of the article of course!
It must be correct because he used percentages!
The revisions section clearly states that the percentages are based on the author's opinion, not statistics!
I am so sick of C# vs VB articles! :crazy:
I used to call my self The Master on forums, then I entered the IT industry and realised how much I still have to learn.
March 22, 2012 at 10:02 pm
luke.bolton (3/22/2012)
patrickmcginnis59 (3/22/2012)
Lynn Pettis (3/22/2012)
patrickmcginnis59 (3/22/2012)
UnbalancedKarma (3/22/2012)
http://www.codeproject.com/Articles/10135/Not-Another-C-Versus-VB-Article?msg=3050761#xx3050761xxThe article is the usual C#/VB snobbery and in-fighting but the linked reply makes some good points in the case for VB.NET.
Comparing the two is always invitation for a massive flame-war, personally I don't think there's much in it (I use C#) although "on error resume next" in VB is a God-Tier feature.
From the article:
"80% of C# programmers are good, while 80% of VB programmers are not good."
I had better file that away for future reference. I can use it as a point of debate!
Whose definition of good?
Nigel Shaw the author of the article of course!
It must be correct because he used percentages!
The revisions section clearly states that the percentages are based on the author's opinion, not statistics!
I am so sick of C# vs VB articles! :crazy:
I'm pretty sure that there was sarcasm in the exchange, it wasn't in defense of the author.
March 23, 2012 at 9:35 am
I purposefully avoided the language comparisions as there is nothing wrong with either as both can accomplish the same jobs.
Popularity is a different and one is clearly more popular than the other.
March 28, 2012 at 8:13 am
In any given version of the framework there'll be a few subtle differences between the two. But MS have a policy of converging them so any new feature that's given to one language will almost certainly turn up for the other in the next version of the framework. And the differences are usually productivity rather than functionality based. You can achieve just about anything you want in either, one just might provide a shortcut.
For me the big difference is that C# doesn't allow you to switch Option Exlicit, Strict and Infer on and off. I don't like the decisions C# makes in this regard but, meh, I can live with them.
Most C# vs VB debates usually end up being about which is easier to type and/or read. C syntax was designed to be terse so it was easy for engineers to type it into text editors. It needed less keystrokes but, as a consequence, was harder to read. Early VB was aiming itself at more casual devs so it's syntax is more verbose. It was slower to type but easier to read. Both C# and VB.Net have kept alot of that early syntax but, in the days of intellisense, it's hard for me to justify C#'s terse syntax. It's actually quicker for me to write "Inherits" in VB that "::" in C# when I've got intellisense support, and it's easier to read too.
I really don't understand why people get so bothered by the differences though. They're trivial and both are very good languages to use.
And On Error Resume Next is not a feature, it's an anachronism which should go the same way as Goto statements and line numbers. To quote a user from another forum: "You're not handling the error, you're sticking your fingers in your ears and shouting 'La La La, nothing to see here'".
March 28, 2012 at 9:11 am
MysteryJimbo (3/9/2012)
Apart from the syntax, you can achieve the same with both so there's little between them since they both use the same .Net libraries.vb does have a stigma associated with it because of its origins but since it became a .Net language this is no longer applicable and is usually in jest.
I'd stick to c# since its similarities to java and c/c++ make it easier to hire for in my opinion hence its popularity
I'd just like to refere to my original post on page one. 2nd reply.
3 pages of one vs the other. pah.
I personally prefer c# as its easier to transpose skills.
Viewing 10 posts - 16 through 24 (of 24 total)
You must be logged in to reply to this topic. Login to reply