3 ms·
Why not just use VB.Net/Winforms?
by scarface74 7y ago
Why not just use VB.Net/Winforms?
- gus_massa 7y agoOriginally: Not a fast enough computer and IIRC the first form editor of VB.Net was not as smooth as the one of VB6. Also it was a language change, let's call it VB#.Net Now: 50% laziness and 50% don't want to migrate a few big projects that only need a tweak per year. If it ain't broke, don't fix it.
- scarface74 7y agoI haven’t tried to install VB6, but you said yourself that it is getting harder every year to install the IDE. What happens when you can no longer install the IDE?
- acqq 7y ago> What happens when you can no longer install the IDE? I guess a virtual machine with Windows 2000 and with VB6 is still smaller than the modern programming environments.
- tluyben2 7y agoDepending in what you need to do; when I last tried, for a legacy system, to run under Wine it was flawless. So by the time it becomes impossible to install I would say Wine will be advanced enough to run all you need. All Windows stuff I need these days works perfectly under Wine. I work a lot with software from almost a decade ago and that mostly just works. Maybe at that time (few years) Wine will run on Windows as well (it has been a long term roadmap feature) to offer just this compatibility layer for old software support without having to install a Windows xp virtualbox.
- kd5bjo 7y agoMicrosoft 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.