All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

A veteran developer asks: What did VB6 get right that modern .NET developers miss?

By

EvilGenius

1mo ago· 4 min readenOpinion

Summary

The author, a veteran developer who shipped hundreds of VB3-through-VB6 line-of-business systems between 1995 and 2010, poses two open questions to the programming community: what did Visual Basic 6 get right that modern .NET developers miss, and what frustrations does the modern toolchain introduce that VB6 didn't? The piece is a reflective call for institutional memory before it fades, seeking honest comparison between the rapid-application-development era of VB6 and the complexity of today's C#/.NET ecosystem.

Key quotes

· 3 pulled
What specifically did VB6 get right that you miss?
What do you find frustrating about the modern toolchain that VB6 didn't make you fight?
I'm trying to get to the root of what was actually good before too much of the institutional memory leaves the room.
Snippet from the RSS feed
Two open questions for anyone who shipped real work on Visual Basic 6 and is now writing C# against modern .NET. What specifically did VB6 get right that you miss? And what do you find frustrating about the modern toolchain that VB6 didn't make you fight?

You might also wanna read