A veteran who shipped ~100 VB3-VB6 line-of-business apps is collecting specific practitioner memories before institutional knowledge disappears, for a book chapter on the VB6-to-.NET transition.
Key Takeaways
Microsoft launched seven UI frameworks after VB6; WinForms (2002) remains the path of least resistance for LOB apps, still built on the form-designer model Alan Cooper sketched in 1987.
The author frames VB6 not as toy or masterpiece but as a design worth reverse-engineering: four-line form event handlers, drag-drop component layout, zero layout code.
The post deliberately avoids leading questions (IDE vs. language vs. ecosystem) to surface categories the author has not anticipated.
Responses wanted: specific workflows or missing features, not general nostalgia or broad complexity complaints.
Hacker News Comment Review
Commenters converge on two concrete strengths: OLE/COM Automation made cross-app scripting trivial, and the WYSIWYG form designer eliminated layout code entirely – both capabilities that modern stacks have not cleanly replaced.
A recurring tension surfaces between architecture and utility: modern toolchains add paperwork that improves structure but slows initial delivery, and AI code generation may partially compensate without eliminating the underlying friction.
The empowerment angle appears repeatedly: VB6 let non-developers (tech support staff, hobbyists) ship real tools, which commenters treat as a feature, not a flaw.
Notable Comments
@Mister_Snuggles: OLE Automation let a VB6 app orchestrate Word, fill templates, and print letters triggered by XML from a Solaris system – cross-platform LOB integration with minimal code.
@2ndorderthought: “Some of the worst code I have ever seen was written in VB. Some of the best tools that awful solved business problems was written in VB.”
