3 ms·
The really-RAD thing doesn’t have a good equivalent today, but I also think developers asked for something that created slightly more maintainable code even if
by alkonaut 7y ago
The really-RAD thing doesn’t have a good equivalent today, but I also think developers asked for something that created slightly more maintainable code even if at the cost of slightly less RAD.
C#/VB with WinForms was the successor to VB6 and doesn’t sacrifice much in terms of development speed but added a lot of modern conveniences (high dpi etc..) that would have cost too much to add to VB6.
- tonyedgecombe 7y agoHigh DPI support in WinForms is a dogs dinner and it didn't arrive until well after VB6 was dead.
- alkonaut 7y agoAdding HighDPI support certainly wasn’t the reason WinForms took the place of VB6, but it’s one of the things that VB6 doesn’t have that WinForms now does (it’s far from great but it’s something). Perhaps better examples of things that were difficult to shoehorn into VB6 apps but first class in WinForms: multithreading, x64, Unicode.