The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
1000x times yes. Oh goodness, I'm spending lines, LINES on syntax that explicitly marks the beginning and end of each statement. OH NO, STOP THE PRESSSES, CANCEL C#, READABILITY IS OVERRATED, all bow to the mighty "more lines on screen = good" crowd.
That is true only because MS deemed it so. They have less support for VB, the business language that built MS. It is a quality language as is c# only with out the } and is intelligent enough to know when the statement ends unlike is single letter counterpart.
Yeah and we told you that their methodology doesn't mean the language is popular IN USE. The TIOBE index is based on search results for keywords. That in no way means the language is more popular in actual use.
Am I a hater of VB.NET? No. I started .NET developement in 2001 with VB.NET, using the command line compilers and Notepad. There was no Visual Studio .NET at the time as the .NET Framework was still a beta.
It doesn't matter what the language is, the money I get for writing in it is still green.
VB.NET is like C# but a bit more verbose and almost like natural English, so anyone can understand VB.NET code.
I always say that's a terrible analogy as spoken language has many nuances that a reader can only understand if provided enough context. You can write something useful with a programming language within a few days or even hours--minutes in some cases. You need weeks, if not months or even years, to become proficient with a spoken language. If that's how VB.NET's defenders choose to extol its virtues, then they're starting off on the wrong foot.
I want my programming languages to clearly reflect the writer's intent without any guesswork. Comparing it with English is not how to sell a programming language to a developer. That's called dumbing it down to help those people not working in this field understand what's being discussed.
I know why this happened.
.net Core 2.1 was announced as supporting VB.
So a whole bunch of C# devs thought, that sounds call, I remeber VB. Lets spend a few hours seeing how amazing a programmer I am and do that application I have been doing for months in 1 day in VB.
10 minutes later.
Stack Overflow - how to error handle.
How do you create string.
Why is there no int64.
1 day later, 100 new questions asking "basic" questions because they have never been asked on stack overflow, with people answering and up voting on mass.
All this in 2 days.
So in comparison, VB.net questions went up 1000% fold (from 1 a month to 1000)
Where as c# questions on went up 1% (from 10,000 a month to 10,100)
At home I use C# and C++\QT on my projects but, at work I am forced to use Visual Basic because, I work with domain computers that will not allow a compiler to be installed. In my office Access is king and we have custom programs written with Access 2016.
I can see why Visual Basic is not dead yet and keeps making progress.
I agree; there is nothing wrong with VB.net. It's a good language; it has it's strengths and weaknesses, just like C# does.
They are not exactly equal in all situations, but close. When to choose one over the other, is mostly a personal preference.
the shop i work in now is only C#, which is fine, but i do miss some of VB.net features. the last one was VB.net and there were some features only in C# that would have been nice to have.
some may argue c# is cleaner than VB.net; once again it depends on who what writing the code. I've seen everything from trash to art in both these languages.
is one language quicker to develop with than the other? no not really.
will one language help you write less code? not really, unless you count "}" vs "end if".
is one easier to learn? from a noob standard, likely VB.net, but you will have to learn a bunch of C# on the way to read the documentation. if someone is experienced in a C style language then C# is likely to get them going quicker.
for all the VB.net haters out there, I've been in development now for 20+ years, I've seen a lot and learned a lot, and frankly language wars are stupid; just use the language that is correct for the situation and let others be.
Last Visit: 21-Jan-20 21:55 Last Update: 21-Jan-20 21:55