Re:The .NET Language Strategy
by wvenable on Wednesday February 01, 2017 @04:59PM
(#13545742)
VB6 used to be awesome though; sure it's really long in the tooth now and doesn't fit into modern workflows but there was a time it was great for banging out apps. I did a lot work in VB6 and I even used it to teach my daughter programming many years ago.
But VB.NET never really seemed to have a point. Why develop a backwards-incompatible language with all the warts of VB? If it was originally much more closely compatible with VB6, you probably still wouldn't be stuck with VB6 code in 2017. And if it didn't try to be so but not quite VB6-like, it would make for better beginners and financial systems language.
Re:The .NET Language Strategy
by cm2187 on Wednesday February 01, 2017 @06:14PM
(#13546407)
There is a case for case insensitive languages (pardon the pun!). You just don't get to write a lot of useless bugs because you mistyped the casing of a particular variable. I see that all the time in C# live demos.
But VB.NET never really seemed to have a point. Why develop a backwards-incompatible language with all the warts of VB? If it was originally much more closely compatible with VB6, you probably still wouldn't be stuck with VB6 code in 2017. And if it didn't try to be so but not quite VB6-like, it would make for better beginners and financial systems language.