> Except few big companies that needs to maintain legacy apps, nobody really cares about VB any more, specially in some brand new dev stack like asp.net core. W

> Except few big companies that needs to maintain legacy apps, nobody really cares about VB any more, specially in some brand new dev stack like asp.net core. Waste of time and resources IMHO. I was a VB dev, and it really made sense 20y ago. Now, I haven't heard somebody is using VB (excluding some bank maybe - but they're mostly stuck in .net 2 or 3). Nope. Not even close. My startup is based on Visual Basic .NET and the .NET Framework 4.0 with ASP.NET and ADO.NET, and IIS. My startup has all new code -- I wrote it all. Currently the code has 18,000 programming language statements in 80,000 lines of typing -- right, lots of comments. No, my startup is not a bank. Instead, my work is for a new Web site where the crucial, core secret sauce is from some original work I did in applied math with some advanced prerequisites in pure/applied math. I really like VB .NET, a lot. I've used a lot of programming languages, and VB .NET is my favorite, by a nice margin. Microsoft did well. C#? No thanks. It borrows some of the syntax from C, and it was designed to be sparse, for the old 8 KB main memory DEC PDP-8, with a deliberately idiosyncratic syntax that is tricky, difficult to read, write, or understand and error prone. It's just too darned sparse. AFAIK, VB .NET and C# are really essentially the same except just for syntactic sugar. IIRC there is a translator from one of these two to the other. Maybe there are some differences, but they have to be for tricky things I likely don't need and don't want to use. So, since VB .NET is much easier to read, write, teach, learn, debug and is less error prone, it's VB .NET instead of C# for my startup. If Microsoft drops, VB .NET, I will scream bloody murder. For functional programming, no thanks. I explained my programming style in https://news.ycombinator.com/item?id=10937342 https://news.ycombinator.com/item?id=10937342 Really, I have no interest in more revolutions in programming style. Instead, I want good tools, and IMHO VB .NET is the best there is. Then I want just to use the good tools. For a tool better than VB .NET, that would be a long shot for a long time. Microsoft: For VB .NET, the .NET Framework, etc. don't mess them up, grow them no more than slowly, keep strict upward compatibility -- don't force me to rewrite or even retest my existing production code. If some users like C# or F#, fine with me -- I won't be using either of them, or A#, B, C, C#, D, D#, ... or G# either except on my piano.