What made VB6 super-productive and quick to get up and running also made it terrible for long-term maintenance, because it hid too much of the details. Then th

What made VB6 super-productive and quick to get up and running also made it terrible for long-term maintenance, because it hid too much of the details. Then there were language warts like set versus let (strong vs weak pointers), for example, which was way above the paygrade of the average VB6 coders; and having to rely on the Win32 API anyway in order to start doing actual work and work around all of its limitaitons. One thing VB6 did do right was forcing interface-based inheritance: Composition over class inheritance was seen as a weakness back then but it was proven as the right concept. This is just my opinion!