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.
It is a lie, You're confounding Classic VB (1998, 20 years old language) with VB.NET (an C# equivalent language).
No, I'm not.
Saying that VB.NET s a C# equivalent is nonsense; they target the same runtime, but so does managed C++. No one in their right mind would compare VB to C++, calling them equivalent. It implies that you could take a VB.NET programmer and drop him/her in an "equivalent" environment. You can't
I did it, I have found not articles about 50% of VB.NET projects fails, again you are lying.
I could offer help, but I'm weirdly enough not in a helpfull mood
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
I'm probably one of those unfortunate that had a manager who felt an urge to develop enterprise level in VB...
From your post I can conclude you are not in the same boat...
The day you will be curious enough to check how TIOBE's index built, you will understand how it is useless and on the same day you will understand how VB is limited...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
From your post I can conclude you are not in the same boat my manager...
Kornfeld Eliyahu Peter wrote:
you will understand how VB is limited
It's pretty much the same as C# though.
Although lately it hasn't been given the same attention as C#.
It works the same for .NET, but I don't even think .NET Core supports VB.
As far as I'm concerned that's Microsoft telling us VB is still supported, but not further developed.
Anyway, that's not really the language's fault...
Ok, so VB is or wasn't supported for .NET Core 1.x, Portable Framework, Unity, some Azure functionality...
It seems VB always comes last for Microsoft, if at all.
And then sometimes, someone, like you, comes along who loves VB and promises to make it all better and it gets a little bit better only for VB to fall behind again.
Yeah, VB was my first language and as such it has a special place in my heart, but I wouldn't recommend VB as a career path for anyone.
Programmers aren't using it, employers aren't asking for it.
It only, somehow, has a high position in a weird TIOBE index.
I would say that such highly hypothetical code has nothing to do with nothing...
I also would say that you do not know how to write efficient code in C#, if you think you have to add all those brackets, or that this is the only way to write it...
You also totally drop the factor of experience... C# can be done in different ways, and be still perfectly readable for the experienced...
It appears with the garbage VB and supposedly identical C# you concocted that you are a master of master of all things! We should bow to you and our soon-to-be VB.NET overlords!
Oh, but wait, what's this? Surely this doesn't work?! You can't have expressions in a C# switch statement!!!
Sorry, but YES YOU CAN, if you know even 1% of C# BASIC syntax...
caseint xx when xx <50 || xx == 42:
for (int x = 0; x <101; x++)
for (int y = 0; y <101; y++)
for (int z = 0; y <101; z++)
L1 = DoSomethingWithL(x, y, z, L1);
L1 = (L1 == 2 ? L1 = 3 : L1 = 0);
caseint xx when xx >390:
L1 = 0;
L1 = 32;
If you love VB.NET, then USE it, we don't care. Just stop embarrassing yourself by trying to "Prove" how much better VB.NET is.
I am proficient in both languages and I prefer C#. That doesn't make me better or worse than you.
All you do with these threads on "VB is better!!!" is tick people off. If that's how you get your jollies, I feel for you.