Re: The Delphi Survey



Bob Dawson wrote:
Shouldn't that make backward compatibility /more/ important? Not sure I see
the coherence of the argument for single source across, for example, win32
and Linux, but not for win32 and .NET.

Not really; the devil is in the details. The nature of .NET development
is very different from native code development. IMO, there is more
capacity and bigger gain for code compatibility with Linux than there is
for code compatibility with .NET. The way development is done on Win32
is similar to the way development is done on Linux: no GC, no runtime,
no large standard library, etc. This isn't the case with .NET; .NET is
very different from Win32.

Certainly abstracting away low-level OS issues is not trivial, and it
was probably easier to provide VCL for .NET than it was to support the
RTL/CLX for Linux.

The difference is that the RTL/CLX offers something on Linux that isn't
available in other tools and is portable between Windows and Linux.
Hence it's a differentiator. .NET's FCL is available from many tools
and makes the code dependent on .NET. Hence, it's the same as other
products.

It's also different because .NET, without Mono support, is a Windows
only technology. This means that there is no inherent business
advantage to porting code from Win32 to .NET. But there is inherent
business advantage to be able to deploy to Linux. The only reason to go
to .NET is to leverage the FCL itself, which is fine, but it's not an OS
deployment advantage, but more like an extension of Windows services.

The final difference is that good Linux support also has the ability to
bring new developers into the community. I don't believe Delphi's .NET
offering has anything for new developers seeking to develop in .NET; IMO
it makes more sense to just use VS.NET.

Code compatibility is only beneficial when that compatibility enables a
significant business advantage and differentiates the product. IMO,
there is little advantage to code compatibility between Win32 and .NET,
but a good deal of advantage between Win32 and Linux. IMO, Delphi could
increase the value of their advantage with .NET by officially supporting
Mono.

--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.



Relevant Pages

  • Re: Linux / Windows GUI application with assembly
    ... before Applications could have been written in Asm, ... under Win32, and the Linux Asm Stuff is still in the ... There is still some assemblers which compile successfully binaries ... under Linux, and I thought someone had already investigated the GUI ...
    (alt.lang.asm)
  • Re: Will there ever be a new Delphi for Win32?
    ... some .NET projects run on Mono directly. ... Calvert's article on running .NET WinForms code on Mono and Linux. ... No. CLX is only supported on Win32 and Linux. ... Yorai Aminov (TeamB) ...
    (borland.public.delphi.non-technical)
  • Re: findfirst, findnext and finddata_t
    ... |> I'm porting a Win32 application to linux. ... The Win32 API appears, based on the little bit posted in this thread, to ... tree walk) and each subsequent item. ... The ftw "package" does not appear ...
    (comp.os.linux.development.system)
  • Re: Interactive sessions on another box from Win32
    ... I planned to ssh to the ... > Expect is not an option on Win32. ... > for connecting securely to linux box and running interactive programs on the ... This is a command line login, or a GUI login? ...
    (comp.lang.perl.misc)
  • Re: Win32 is *not* killed.
    ... > eventually adding Win32 and Linux to the Octane IDE in future releases, ... in the open door to confusion. ... linux support then fine. ... projects now and provide full cross support later. ...
    (borland.public.delphi.non-technical)