Linked by Thom Holwerda on Mon 11th Jun 2012 00:38 UTC, submitted by judgen
Windows "Microsoft recently extended 'It Just Works' compatibility for Visual Basic 6 applications through the full lifetime of Windows 8. Visual Basic 6 first shipped in 1998, so its apps will have at least 24 years of supported lifetime. Contrast that with the Microsoft .NET Framework 1.0 (2002), which is incompatible with Windows 7 (2009)."
Thread beginning with comment 521792
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: kill -9 now...
by jptros on Wed 13th Jun 2012 01:27 UTC in reply to "RE[4]: kill -9 now..."
jptros
Member since:
2005-08-26

Microsoft is finally starting to treat application development for what it is - a fairly complex process that requires tools that allow programmers to impose rigid processes on themselves to get good results. .NET has those tools, VB6 doesn't and never did.


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

Reply Parent Score: 2

RE[6]: kill -9 now...
by galvanash on Wed 13th Jun 2012 02:08 in reply to "RE[5]: kill -9 now..."
galvanash Member since:
2006-01-25

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.


THAT is what you bring up to defend VB6???

http://stackoverflow.com/questions/2703681/winforms-vs-wpf

http://10rem.net/blog/2010/11/16/windows-forms-developers-tell-me-a...

Winforms is a dead end. Use WPF. Or use Qt with native bindings if you feel adventurous.

Your complaint is a tooling issue, not a programming issue - winforms is not the only option available for a .NET developer and in fact is probably the poorest one.

Sure winforms is easy, so is VB6 - the point is both of them have the same problem... They scale poorly with developer need, you hit walls with either of them that cannot be easily overcome. That is why Microsoft is desperately trying to get their developers to see the light and stop using these technologies...

If you simply can't stomach the MVC/MVVM paradigm Delphi is still around if you have the money for it and want something more like VB6 but with "teh snappy". It was and still is far faster than any version of VB as far as the resulting UI performance goes (that includes VB6). Hell, it is faster than VB6 by pretty much any measure, and it is fairly portable to boot. The feature set and layout control in Delphi are about an order of magnitude more flexible than VB6 every was - but it is the exact same development workflow as far as how the GUI stuff works.

VB6 forms being "fast" is a side-effect of it being almost 15 years old and woefully lacking anything resembling a modern feature set. It is archaic. That is not a strength...

Reply Parent Score: 2

RE[7]: kill -9 now...
by jptros on Wed 13th Jun 2012 03:33 in reply to "RE[6]: kill -9 now..."
jptros Member since:
2005-08-26

Right well, so in other news, VB6 will continue to be supported if for no other reason than no business sees the value in investing in complete rewrites because some developer on an internet forum thinks VB is trash. Apparently Microsoft agrees.

By the way, I'm a .net developer, c#. I've inherited and still support to this day my fair share of VB projects, some crap, others not. I don't have a soft spot for Visual Basic but I've seen plenty of it's success in the business world first hand.

Reply Parent Score: 2

RE[7]: kill -9 now...
by snorkel1 on Wed 13th Jun 2012 15:42 in reply to "RE[6]: kill -9 now..."
snorkel1 Member since:
2012-02-25

"Winforms is a dead end. Use WPF. Or use Qt with native bindings if you feel adventurous. "

Use Lazarus and or Delphi instead. WPF is probably not going to last either.

last time I tried to use WPF it had a very unfinished feel to it.

Reply Parent Score: 1