On: The chronic suffering of the VB.NET community

[rufius]

Why uhhh... why wouldn’t people just start writing new components in C#. Surely learning C# is not beyond them?

It’s not like there’s a compatibility issue. Just stop writing it.

[czechdeveloper → rufius]

There are 1 to 1 transpilers between languages (with few exceptions such as LINQ to XML in VB) that are really good.

I've migrated hundreds of thousands lines of VB to C# in past years.

[aljarry → czechdeveloper]

Had similar experience - I transpiled a ~120kLOC legacy winforms app in day and a half - mostly spent fixing build errors between not exactly translatable elements / missing rules in transpiler.

[contextfree → rufius]

what if they don't want to?

[chrisseaton → contextfree]

Are they going to pay Microsoft enough to maintain VB.NET just for them?

Or they could re-implement and maintain VB.NET themselves?

Those are their options. You can't just demand that someone provide you a product if they don't want to.

[eropple → contextfree]

They're welcome to maintain their own ecosystem. Microsoft made it clear over a decade ago that VB.NET was symptomatic treatment at best.