News for hackers. Stuff that matters.

A comment on The .NET Language Strategy. Parent comment

Re:The .NET Language Strategy by scarface74 on Wednesday February 01, 2017 @11:52PM (#13548207)
It's not about sneering a VB. I don't see the use of it in 2017. I started using VB6 in 1999 - 2000. I was a pretty good C and C++ programmer, I could do a little MFC, I was pretty good at writing COM and DCOM dlls in C++, etc. but I saw a real advantage of VB to getting used friendly GUI apps done and the IDE was pretty good. I would often wrap c++ code in ATL wrappers to create COM objects to use in VB.

But what's the real purpose of VB today? No matter how you look at it, either C# is just as easy as VB.net or VB.Net is just as complicated as C#. It seems just wordier and redundant.

[ Parent | on HN ]
Re:The .NET Language Strategy by smoothdeveloper on Thursday February 02, 2017 @12:32AM (#13548357)
Nowadays, do you use any language which is not C like?

Regarding VB, the language is used by many people whose main occupation is not software development, and even for those doing software there are many who find C# or similar looking languages aren't a panacea (I do, and have around 15 years of C# experience).

In some cases VB is also less redundant than C#, it has better type inference for example.

I'm sure plenty of pascal/delphi developers are also fine without C#.

You should understand that other languages than C/C++/C# make different syntax choices, and it is not hurting C# in anyways that such language exist and prosper.

Note that I had a lot of prejudice against VB but I came back from that perspective, and in the meantime, I feel additions to C# language push it in territory where the syntax is getting really noisy / clumsy (I've picked up F# so I use that it as a metric).

[ Parent | on HN ]
Re:The .NET Language Strategy by averagewall on Thursday February 02, 2017 @06:52AM (#13549854)
I'm just waiting for a robust VB to C# converter or at least a way to start moving code across gradually. For now, I'm locked into VB because of a huge code base that's all one giant assembly. It'd be great if you could put C# classes in a VB program (not as dlls), then we might see some VB programmers just stop using it for new features.
[ Parent | on HN ]