Free Republic
Browse · Search
News/Activism
Topics · Post Article

To: PatrioticAmerican
"There are far better reasons to continue the naming of a product more than there are to change it."

Sadly, your post was a complete non-sequitur. No one was arguing about the name.

What started my posts on this thread was that I responded to someone who claimed that VB.Net was backwards compatible.

You took issue with my response and claimed that it was my VB 6 code that sucked, rather than a compatibility issue. You went on to cite your own 25,000 LOC VB 6 program that "converted" easily to VB.Net.

But both you and the original poster are in error. VB.Net is NOT backwards compatible with VB 6. Conversions don't qualify as backwards compatibility, contrary to your uninformed cries to the contrary. The forms properties in VB 6 are not 100% supported by VB.Net. Various language commands in VB 6 are not supported in VB.Net.

Note that I did not say that VB.Net was bad, only that it was not backwards compatible with VB 6.

And that has nothing to do with a name change or your program successfully "converting," as any serious programmer will tell you.

Perhaps if you were able to pay more attention to what was said, you'd be taken more seriously yourself.

70 posted on 05/05/2002 2:18:07 PM PDT by Southack
[ Post Reply | Private Reply | To 68 | View Replies ]

Free Republic
Browse · Search
News/Activism
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson