4 ms·
Microsoft made fundamental changes to the Visual Basic language in order to make it run on the CLR, to the point that it feels more like an alternative syntax f
by kd5bjo 7y ago
Microsoft made fundamental changes to the Visual Basic language in order to make it run on the CLR, to the point that it feels more like an alternative syntax for C# than the successor of VB6– the superficial similarity between 6 and .Net caused lots of false-friend problems during he transition and most projects would have been better served by being rewritten in C#.
- alkonaut 7y agoWhat were the biggest benefits that people got from switching? Where does VB6 most show it’s age? No modern looking controls? Harder to use Unicode?
- scarface74 7y agoBeing able to get a job and not being a “VB developer” for 15 years, the company lays you off, you look for another job and find that no one wants to hire “VB developers”. Then post on HN and Reddit and scream “ageism is rampant on our industry”. Disclaimer: I’m 45.
- kd5bjo 7y agoA lot of VB programming was connecting together 3rd-party COM components, which had to be written in C/C++. After the CLR came along, those vendors slowly stopped supporting VB6 with their new releases as they moved their codebases and workflow to the new system.
- pjmlp 7y agoThat was only true for early VB versions. VB6 had full support for native AOT compilation and creation of OCXs in pure VB code.