Re: Turbo Basic Explorer


"I.P. Nichols" <nospam@xxxxxxxxxx> wrote in message
news:450abfb0@xxxxxxxxxxxxxxxxxxxxxxxxx
"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.

At least for now, VB6 still works. Many haven't moved anywhere yet. The
uptake of VB.Net is abysmal compared to what they planned and expected. The
uptake of .Net overall has been affected by this.

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.

The key word here is "deprecation". I'm not in favor of "never changing"
anything. There is a right way and a wrong way, as well as right reasons
and wrong reasons, for making breaking changes. Extensions are wonderful.
Change is good, done correctly.

The code breaking changes MS made to VB were senseless. The extensions were
great. They were not mutually exclusive (which is what the marketeers would
have you believe). Those wanting to argue that need only look at IL and/or
talk to the VB dev team (if you can get through the marketeer firewall).

Dan


.

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: VB6, VB2005, or Something Else?
    ... that Microsoft focused only on most common use of VB6 as a database ... true X uses this feature of a language figure is near impossible ... There are breaking changes but they are in the order of the UNICODE ... found that this also included VB6 applications, ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... true X uses this feature of a language figure is near impossible ... There are breaking changes but they are in the order of the UNICODE ... from Microsoft and can automatically convert projects developed in previous ... found that this also included VB6 applications, ...
    (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: Turbo Basic Explorer
    ... "People," AFAICS, argue that Delphi might ... be attractive to VB6 developers not because migration to VB.NET is ... to avoid breaking old code. ... There are those who have made the argument that for Microsoft to have ...
    (borland.public.delphi.non-technical)