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 521523
To read all comments associated with this story, please click here.
VB6.....
by modmans2ndcoming on Mon 11th Jun 2012 02:22 UTC
modmans2ndcoming
Member since:
2005-11-09

An abomination of a language. You don't have to make something complex to make it easy to use....look at Python. it adheres to common sense design for a language and is simple to learn and use.

Reply Score: 8

RE: VB6.....
by Kroc on Mon 11th Jun 2012 06:47 in reply to "VB6....."
Kroc Member since:
2005-11-10

look at Python


Look at the whitespace. It's hard enough to explain to not double-space in HTML or to use Tab instead of tons of spaces to align things in Word. Many regular users do not understand or care about the semantic differences of tabs and spaces. If the text is indented yay-much, then that should be fine.

Reply Parent Score: 6

RE[2]: VB6.....
by galvanash on Mon 11th Jun 2012 08:03 in reply to "RE: VB6....."
galvanash Member since:
2006-01-25

Look at the whitespace.


Sorry Kroc, but that is a red herring. We are talking about teaching non-programmers to program right?

"Lesson one: In python white space means something. This is how it works.... [explanation]"

Beginners have no problem with this. In 15 minutes the whitespace issue is gone. There is nothing technically challenging at all about whitespace being significant - it is simply a different way to establish block scopes. Teaching them the hows and whys of block scoping is the hard part, not the syntax to do it.

The people this issue really bothers are the ones who have done programming in other languages where whitespace isn't meaningful. It makes their brain itch because it just seems like something is missing...

That isn't because it is a bad idea - it is just different. Different is not necessarily bad (or better) - it is just what it is... I program in 8 different languages on a regular basis, two of which are Python and Ruby. The whitespace thing is a non-issue once you get used to it - most people (me included) eventually learn to like it even. It makes complete sense once you step back and look at it for what it is.

Reply Parent Score: 8

RE[2]: VB6.....
by Soulbender on Mon 11th Jun 2012 10:38 in reply to "RE: VB6....."
Soulbender Member since:
2005-08-18

Many regular users do not understand or care about the semantic differences of tabs and spaces.


Regular users don't program in Python nor in VB. If you're going to use either you just have to learn how things are done. At least it's not PHP...

Edited 2012-06-11 10:38 UTC

Reply Parent Score: 4

RE[2]: VB6.....
by kwan_e on Mon 11th Jun 2012 11:43 in reply to "RE: VB6....."
kwan_e Member since:
2007-02-18

It's hard enough to explain


Teaching is a different task to doing. Some things may be harder to teach. But the changes should be made to the teaching method.

Reply Parent Score: 4

RE: VB6.....
by WorknMan on Mon 11th Jun 2012 06:58 in reply to "VB6....."
WorknMan Member since:
2005-11-13

An abomination of a language. You don't have to make something complex to make it easy to use....look at Python. it adheres to common sense design for a language and is simple to learn and use.


And how far along was Python in the mid-late 90's, when VB was at its prime? Even now, although there's some GUI frameworks, there isn't (AFAIK) an IDE for rapid application development in Python that is as robust as the one in VB6.

As for .NET, is it even relevant anymore now that Metro and WinRT are on the scene? Are developers expected to start all over again every 3-5 years (from COM to .NET to Winforms to Silverlight/WPF to Metro) when MS changes its mind and decides that a technology that it 'bet the company on' should be replaced by a new technology that they're betting the company on?

Reply Parent Score: 3

RE[2]: VB6.....
by galvanash on Mon 11th Jun 2012 07:18 in reply to "RE: VB6....."
galvanash Member since:
2006-01-25

And how far along was Python in the mid-late 90's, when VB was at its prime?


There was Delphi though - and a few others. You can't blame VBs popularity on lack of alternatives - it was simply targeted at a very particular demographic - people who wanted to write programs but didn't want to learn how to write programs. It sold immensely well to that market...

I'm sure I will piss off some people with that comment, but the truth hurts. I did some pre.NET VB way back in the day (had no choice), but thankfully I learned a real language or two first so the long-term damage to my brain was minimal.

To the VB apologists out there: If you cut your teeth on VB but have since moved on, good for you - but if you don't realize by now how insanely, unforgivably, mind-numblingly bad it was... I have news for you - you still don't understand basic programming.

Reply Parent Score: 5

RE[2]: VB6.....
by lucas_maximus on Mon 11th Jun 2012 08:31 in reply to "RE: VB6....."
lucas_maximus Member since:
2009-08-18

As for .NET, is it even relevant anymore now that Metro and WinRT are on the scene? Are developers expected to start all over again every 3-5 years (from COM to .NET to Winforms to Silverlight/WPF to Metro) when MS changes its mind and decides that a technology that it 'bet the company on' should be replaced by a new technology that they're betting the company on?


TBH someone always says this. The .NET framework hasn't fundamentally changed since 2004-2009. Even with the update to 4.5

Most of the same techniques and technologies learnt for Silverlight WPF is pretty much the same as those that one would use in Metro.

Reply Parent Score: 4

RE[2]: VB6.....
by moondevil on Mon 11th Jun 2012 10:24 in reply to "RE: VB6....."
moondevil Member since:
2005-07-08

COM to .NET to Winforms to Silverlight/WPF to Metro when MS changes its mind and decides that a technology that it 'bet the company on' should be replaced by a new technology that they're betting the company on?


Since Windows XP most Win32 APIs are actually COM based.

All the .NET APIs for native code to interact with a running .NET VM are COM based.

Metro is COM based and you can use it flawlessly from .NET.

The way Microsoft replaces the framework of the day, is no different than what other companies do.

Reply Parent Score: 3

RE[2]: VB6.....
by modmans2ndcoming on Mon 11th Jun 2012 23:42 in reply to "RE: VB6....."
modmans2ndcoming Member since:
2005-11-09

How did a comment complaining about VB6 compared to Python turn into attacking some non existent argument about.net?

Reply Parent Score: 3