OSNews

Except that large Win Forms applications that have to work with large datasets and have lots of user controls perform like garbage and even worse under Windows 7. VB6 on the other hand, as ugly as the code might be, handles things just fine so next time you feel like preaching about why VB6 should be dumped please provide us with an example of a RAD environment that does more than produce prettier code. Yes, C# and even VB.Net are much better languages from the developers point of view but the bottom line is they haven't filled the shoes that VB6 currently wear which is why no one is going to chunk their investment in favor of a complete rewrite for what? A new data entry application that lags, pauses and flickers when the datasets start getting some meat? The code looks nicer and the error handling is much better though! Seriously though, if these terrible VB6 programmers did that bad of job when they wrote the applications they would have already died but the truth is, the code has been written well enough that people have been able to maintain it for all these years that Microsoft feels a need to still support running them on newer versions of windows. Yes, there are turds floating around in the toilet bowl but they get flushed usually sooner than later. We (professional developers) all get some steaming pile of crap dumped on us at least once in our careers and the syntax ain't always Visual Basic.

Edited 2012-06-13 01:29 UTC