Re: Turbo Basic Explorer



"Craig Stuntz [TeamB]" wrote:

It's a straw man argument. "People," AFAICS, argue that Delphi might
be attractive to VB6 developers not because migration to VB.NET is
"hard," but because Microsoft cannot be trusted to break the language
definition yet again in the future, as they have done in the past. The
problem with VB.NET isn't just that effort -- a substantial or total
rewrite -- is required to move VB6 code, but that having spent that
effort it is not clear that it won't be required when the "next" flavor
is required.

While that is an extremely powerful argument, it apparently hasn't been
compelling judging by the number (admittedly speculative) of VB6ers that
have come over to Delphi.

With Delphi there is historical evidence that Borland goes to lengths
to avoid breaking old code.

There are those who have made the argument that for Microsoft to have
transitioned VB6 to VB.NET without breaking much of the language would have
been a case of visiting the sins of the father on the child. And yes, I know
the counter argument effectively made by Dan Barclay.


.



Relevant Pages

  • Re: Delphi? Futureproof re vb!
    ... .NET side of things over the older syntax side. ... Delphi experience will be along to address these issues. ... Apparently dot net express is an attempt by Microsoft to get back ... to the vb6 concept which they should never have left! ...
    (microsoft.public.vb.general.discussion)
  • Re: Delphi? Futureproof re vb!
    ... Does RealBasic have OCX support? ... | thought I heard they were moving toward a .NET implementation of Delphi, ... | As for me, when the day comes that VB6 is "no more", my preference will be ... |> by Microsoft to get back to the vb6 concept which they should never have ...
    (microsoft.public.vb.general.discussion)
  • Re: Delphi? Futureproof re vb!
    ... I haven't looked at it recently, but I thought I heard they were moving toward a .NET implementation of Delphi, although I'm guessing they are remaining backward compatible with their old syntax. ... The book so far has about a fifth of the space taken up saying in effect what a retrograde step vb net is, thought up by programmers thinking as programmers and not users, with the "help" even worse, and that VB express is an attempt to "go back". ... About a twentieth of the book gives new syntax, and the whole of the rest describes programming concepts which are easy to understand and are in fact exactly as vb6. ... Apparently dot net express is an attempt by Microsoft to get back to the vb6 concept which they should never have left! ...
    (microsoft.public.vb.general.discussion)
  • Re: Turbo Basic Explorer
    ... "People," AFAICS, argue that Delphi might ... be attractive to VB6 developers not because migration to VB.NET is ... There are those who have made the argument that for Microsoft to have ... The code breaking changes MS made to VB were senseless. ...
    (borland.public.delphi.non-technical)
  • Re: Microsoft not content with "dissing" just the Classic VB Developer Army....
    ... I've read the petition and I can't ... Microsoft can satisfy the "issues" in the petition (which pretty much boil ... Nothing but adding unmanaged VB6 into the VS.NET IDE ... COM interop support, a poor code conversion wizard, the ending of mainstream ...
    (microsoft.public.dotnet.languages.vb)