C# over VB.net
-
VB is pure evil ! :laugh: (And my sigh makes you agree immediately ;P)
V.
(MQOTD rules and previous solutions)OriginalGriff wrote:
V is absolutely right
No, that's the problem. It's not evil - it's just not very good. But...it seems "OK" and it's easy to teach - which is not the same as easy to learn - and that means that lazy teachers use it because it gives them less to do... :sigh: And then the students escape into the real world and - it being the only thing they know - carry on using it, despite the problems it causes, and because they know no better they assume that it's horrible weaknesses are in fact it's strengths. So they defend it to the death despite having nothing useful to compare it with.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
-
VB isn't a bad language - it's just is too wordy and weakly typed - it makes decisions for you that C# won't and that can get you into lots of (run-time) trouble that C# catches at compile time. VB also still has ON ERROR RESUME NEXT for which it should be buried in quicklime and left to rot... Having said that, I code in C# - and use online translators for the very occasional times when I need it in VB...
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
Once upon a time, my company decided to bring our code base from DOS to Windows. We bought 3 months in the local Microsoft DNA Lab (DNA - Distributed Network Application) to learn about our chances. At the very first meeting Microsoft's expert outlined a working framework, that in it's center there was the - then new - Visual Studio 6, and recommended VB6 as the best option we have. We believed him and started to prototype the new system. After two and a half day we started to hit barriers from every direction. After two weeks we just moved to C++. The funny thing is that our original - DOS - code was in C++, so we was able to reuse a lot of it without any change...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
No, that's the problem. It's not evil - it's just not very good. But...it seems "OK" and it's easy to teach - which is not the same as easy to learn - and that means that lazy teachers use it because it gives them less to do... :sigh: And then the students escape into the real world and - it being the only thing they know - carry on using it, despite the problems it causes, and because they know no better they assume that it's horrible weaknesses are in fact it's strengths. So they defend it to the death despite having nothing useful to compare it with.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
-
VB isn't a bad language - it's just is too wordy and weakly typed - it makes decisions for you that C# won't and that can get you into lots of (run-time) trouble that C# catches at compile time. VB also still has ON ERROR RESUME NEXT for which it should be buried in quicklime and left to rot... Having said that, I code in C# - and use online translators for the very occasional times when I need it in VB...
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
One thing that I like with VB over C#: No need for all the friggin' brackets and semicolons. :) I fail to see why any program language in the 21st century needs a line terminator... :doh:
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
I'd just like a chance to prove that money can't make me happy.
Me, all the time -
One thing that I like with VB over C#: No need for all the friggin' brackets and semicolons. :) I fail to see why any program language in the 21st century needs a line terminator... :doh:
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
I'd just like a chance to prove that money can't make me happy.
Me, all the timeThat's one of the advantages of C# over VB - it doesn't need a line continuation character, because it has a statement terminator! (In exactly the same way, and for the same reason, as an English sentence does). :laugh:
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
-
One thing that I like with VB over C#: No need for all the friggin' brackets and semicolons. :) I fail to see why any program language in the 21st century needs a line terminator... :doh:
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
I'd just like a chance to prove that money can't make me happy.
Me, all the timeSemicolons aren't line terminators, you can have a single statement spread over multiple lines, and multiple statements on one line. Both can be useful when statements are very long or short respectively (though coding standards tend to ban the latter because they're stuck in 1990 when lines had to be really short).
-
One thing that I like with VB over C#: No need for all the friggin' brackets and semicolons. :) I fail to see why any program language in the 21st century needs a line terminator... :doh:
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
I'd just like a chance to prove that money can't make me happy.
Me, all the time -
That's one of the advantages of C# over VB - it doesn't need a line continuation character, because it has a statement terminator! (In exactly the same way, and for the same reason, as an English sentence does). :laugh:
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
-
Although compilers don't need line terminators, I actually really like them because they help me read my code :-) They provide my eyes with a clear "stop going left and move down" signal.
CarefulCoder wrote:
"stop going left and move down"
You read your code right-to-left in Australia? :omg:
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
I started programming .net in VB and I didn't understand why all the C# programmers complained about how bad vb.net programmers are. Then I got a new job programming in C#. I did that for about 4 years and took a new job that was back in vb.net. I now understand why C# programmers were complaining. I now dislike vb.net programmers just like they did. I really miss programming in C# at work.
There must be a full moon, the Microsoft haters are out complaining again about VB. C# is a Microsoft product that was created less than 10 years ago about the same age some C# programmers behave. It was adopted into the .net framework which is by the way in VB land. While you C# code-cist, Microsoft haters enjoy Visual Studio, another tool in VB land there isn’t that much difference between any language except for its intended use and the implementation. I write C# and VB and many other languages to get the job done. Anytime I need to translate between these two languages I use a tool like the Telerike Convertor and find that the differences are very small. About as small as the issues that you bring up. But I have heard it all before, you have VB code examples that are very poorly done just like JavaScript. Maybe when you C# Microsoft haters have been around as long as VB then there may be some poor examples that will turn up as well. I have add enough of the rubberneckers in this forum and closing my account down.
-
VB isn't a bad language - it's just is too wordy and weakly typed - it makes decisions for you that C# won't and that can get you into lots of (run-time) trouble that C# catches at compile time. VB also still has ON ERROR RESUME NEXT for which it should be buried in quicklime and left to rot... Having said that, I code in C# - and use online translators for the very occasional times when I need it in VB...
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
I agree 100% with this. Would also like to add that VB has a poor implementation of Linq and Lambdas. And I really can't stand Option Explicit and Option Strict. Shouldn't even be an option, they should always be on.
