3 ms·
Both vb.net and C# compile to the same bytecode. So fundamentally, if you code for a hobby or are a lone coder, it's down to what you prefer (I prefer vb.net ov
by Jaruzel 4y ago
Both vb.net and C# compile to the same bytecode. So fundamentally, if you code for a hobby or are a lone coder, it's down to what you prefer (I prefer vb.net over C#), however organisations made it clear early on that C# was much preferred so that's what prevailed.
If I'm quickly knocking up a small GUI utility then the drag-drop building nature of a vb.net forms app is a real time saver - but in contrast you have more flexibility if you build controls via code like C# does.... horses for courses really.
Bizarrely, I've recently started exploring using C# as a CGI back-end via .NET core on Linux... for the simple reason that I can. Apparently it can be quite performant.
- ycuser2 4y agoMicrosoft does not develop VB.NET further.
- zozbot234 4y agoIsn't the Roslyn compiler open source? It might be possible to maintain a fork and bring the language to parity with upcoming C#/.NET features.
- pjmlp 4y agoThey do, but not adding features to please us language geeks, rather what makes sense to interop with .NET libraries, CLS compliant. Roslyn for VB.NET still gets more love than F# across .NET workloads. Now it is true that they could rename CLR into C# Language Runtime, given the extent of effort that C# gets, versus VB.NET, F# and C++/CLI.