3 ms·
It has kept some of its niceties. It's one of the rare case insensitive languages (less pointless bugs as a result of typos), it is very expressive (I just don'
by cm2187 10y ago
It has kept some of its niceties. It's one of the rare case insensitive languages (less pointless bugs as a result of typos), it is very expressive (I just don't get the love of certain programmers for special characters), and it provides a natural evolution for business people into programming, many of who even today have learned the basics of coding with VBA (like me...).
And there aren't that many breaking changes between VB6 and VB.net. Enough to make a VB6 program not compile. But not enough to really stand in a way of a VB6 programmer upgrading his skills over a couple of weeks.
- wvenable 10y ago> And there aren't that many breaking changes between VB6 and VB.net. If you just count syntax, maybe. But the entire environment and API of VB6 wasn't there, making the transition pointless. It's like arguing that Windows C programmers have an easy transition to C on Linux because it's the same language. VB.Net in it's current form should never have existed. VB.Net should have been able to run VB6 applications unmodified giving a straight forward transition from VB/VBA to .Net. Instead most apps were never ported from VB6 and VBA. It was a huge missed opportunity.
- voltagex_ 10y agoOooh, I wonder how hard it would be to make a VB6 compiler with Roslyn...
- umanwizard 10y agoLike I said: lexical syntax. Case sensitivity and whether you use "End" or "}" are, to me, down somewhere around tabs vs. spaces in terms of what matters for the usability of a programming language.