It's definitely used that way, but it's not that it's a bad language.

Really it has the PHP problem: lots of new (inexperienced) programmers use it, and so there seems to be a disproportionate amount of their not-very-good code floating around out there. The implication of course is that if you find some random project written in VB.NET, there's a higher-than-average chance[1] that it's not great quality.

For what it's worth, there's actually quite a few features in VB.NET that aren't in C#[2], though honestly not many that are compelling enough to switch. The reverse is actually not true: There's really nothing you can do in C# that you can't do in VB.NET, though in many cases the syntax is slightly more awkward (lambdas, ternary and coalesce operators come to mind). In many cases (plain procedural code) the only difference between the two is semicolons and how you end code blocks (if/for/while/etc).

All that said, these days I'd be surprised if anyone chooses VB.NET over C# for anything new. IMHO C# is still a much nicer language.

[1] Not at all scientific, only my personal observation [2] https://en.wikipedia.org/wiki/Comparison_of_C_Sharp_and_Visu...

As someone who used to use mRemote everyday, all day long (change of jobs since then and the work I do now doesn't require it) I can say that mRemote(ng) is super stable, especially considering what it does. And I used the app more than any other on my computer, apart from Chrome, and it rarely had any crashes. The fact that it had barely any updates for years but was still so stable is a testament to how well it was written, regardless of it being written in VB.

And just because a language is used for teaching and not necessarily designed for super robust applications, doesn't mean something written in it isn't useful or dependable.