3 ms·
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. Ju
by rufius 7y ago
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 7y agoThere 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 7y agoHad 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 7y agowhat if they don't want to?
- eropple 7y agoThey're welcome to maintain their own ecosystem. Microsoft made it clear over a decade ago that VB.NET was symptomatic treatment at best.
- chrisseaton 7y agoAre 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.