Wiki Home

Visual Fred


Namespace: WIN_COM_API
A former Microsoft VB product manager, Bill Vaughan, is credited as having coined the name "Visual Fred" for "VB.Net" --a name chosen to emphasize developers' claims that VB.Net represents such a radical departure from VB that it shouldn't be considered a mere upgrade.
Visual Basic, as it was once known, is dead.
See also: http://www.mvps.org/vb/index.html?rants/dotnot.htm
Beyond the datatype issues (which are most of the list it seems), here's some things that really surprised me from the list above...

"The Immediate window will not work in Design mode" - Being that I really liked the Immediate window when I worked with Access years ago, I'm glad I still have the command window in VFP6/7.

"The Name property for forms and controls is not exposed at runtime." - Maybe I'm just weird, but this seems pretty strange to me.

"Parenthesis are not optional when calling procedures." - I like this. But I hope it also becomes a standard for the WSH. I've had one nagging wish ever since I started to code in both VB and VFP - that syntactical differences for common logic constructs would either become more cross-platform compatible or disappear altogether. Why should I have to remember the way functions/procedures are called, or the way an IF or DO CASE statement is assembled, between languages? - William Fields
Because they are different languages? Seriously, the people that gripe about the differences between VB.NET and C# are really just big whiners that would like their job to be done for them. JMO -- Mike Helland
WWAAAAA!!!! - Wf
Hopefully, we can all learn to confine our criticism to statements that have some CONSTRUCTIVE purpose. Anything else is simply ego wars which should be taken elsewhere. If Mr. Helland has some constructive reason why the syntax should remain different as the languages evolve, I would love to hear it. -- Ray Kirk

Mr. Helland is my Dad's name. Anyways, why have two languages with the same runtime, IDE, and syntax? Seems like a whole lot of money and wasted energy to me. If I decide I'm gonna use Java instead of VFP, do I have the right to complain that Sun messed up cause the syntax is way different than what I'm used to? Sure. But does someone else have the right to claim that my complaint makes no sense, and then call me a whiner for wanting my job done for me? You bet. Some of the VB folks are complaining that there are differences in the syntax between two languages... holy crap, Not that. The reason VB.NET exists is simply to get VBers to .NET with minimal amounts of syntax changes. C# is to get C++ and Java people onto .NET. If you're so distraught that the languages are different and you have to remember both of them, don't. Learn one and not the other.

Standardisation helps people. That's why both Cadillac and Ford have the same sort of indicator toggles. As for syntax, maybe it is a good idea for VFP to make THEN a protected (and ignored) word so we can implement VB-like IF...THEN conditionals. Ditto CASE...ENDCASE/IF...ELSEIF...END IF which are functionally the same between VFP and VB.
Having said that, in the US you would spell "standardisation" as "standardization". The lack of it does not prevent our communicating.-JR

I'm not suggesting that the languages be identical. But, for those commands and functions that are equivalent between languages, it would be useful if they had identical syntax. I don't expect VB to have a local data engine with its various supporting commands and functions. I don't expect VFP to have some of the features of VB or C. But, I would hope that all could agree that if I want to extract the third character of a string, then it would be helpful if all languages used the same syntax. In VFP it would be SUBSTR(string,3,1). I dare say that in VB and C it would differ. WHY?

Because they're two different languages, orginally written by two different compaines, for two different developer backgrounds. You can't take three langauges and evolve them to similar syntax and be left with a single elegant, clean, language. It perverts it. VB is based on BASIC, which was written long ago. VFP is based on xBase syntax, which was written long ago. To say that "its stupid they aren't the same" is pretty unrealistic.

And we're not talking about a function that extracts a string with certain parameters here (VFP's SubStr()), we're talking about how functions and procedures are called in two different environments, theres a huge differnce. In VB and C# the SubStr() types of things are consistant, because of the .NET framework classes that handle it, however, the use a parathesis in calling function is differnt because thats the way they were before .NET (VB is a .NET langauge for people used to VB6, C# is a .NET language for people used to C++ and Java). -- Mike Helland
Category VBConcepts
( Topic last updated: 2001.08.01 03:36:37 PM )