Re: Vendor says nobody uses Delphi anymore ...

From: Paul Dolen (nospam_at_nowhere.com)
Date: 11/23/04


Date: Tue, 23 Nov 2004 14:19:08 -0600


>One of our vendors wants to convert their app from Delphi to VB.Net.
>
>Why?

Well, I just don't know enough about .NET yet. My company is moving
to .NET, so I need to learn more. But, I think that in your case of
moving from Delphi to VB.NET, there are two separate issues. The
first is if there a specific need to move to .NET. Then, if there is
a need to move to .NET, which .NET language to use is really a
separate question.

So, if there isn't any good reason to go to .NET, then I'd certainly
say that moving from Delphi to VB.NET makes no sense. Now, if there
is a reason to move to .NET, then obviously Borland would say that
Delphi.NET is the reasonable route to go. After all, it should be a
quicker port. But, I can sort of see how someone would think that if
they are going to change platforms, they might as well move to a more
"standard" language in .NET. I think if I was going to pick a .NET
language other than Delphi, I'd choose C# over VB. But, I do
understand that the VB.NET language is much improved over the old VB6
language. I haven't used it, but I understand it has exceptions more
like Delphi, for example.

The bottom line to me is, what does management think they are getting
by moving to VB.NET? Do they think they can get more qualified
developers? Do they think that the vendor (MS) is more stable and
likely to support the product better? Are there real needs to use
.NET?



Relevant Pages

  • Re: where do us long time VBers move on to?
    ... They have no history with the language and do not even know ... > Delphi also has some risks, but they seem fairly well mitigated. ... the user base is significantly larger ... > It's not easy moving your code base, ...
    (microsoft.public.vb.general.discussion)
  • RE: where do us long time VBers move on to?
    ... One of the most negative things written (in comments, not necessarily reviews) about VB.Net is that it is object-oriented. ... > Yet it appears we're going to Delphi. ... They have no history with the language and do not even know ... > It's not easy moving your code base, ...
    (microsoft.public.vb.general.discussion)
  • Re: Delphi? Futureproof re vb!
    ... Might I just say, that going to Delphi, is probably not a wise choice. ... then you need to choose a language that either has a standard attached ... Standardized, Multiple Vendors, lots of available tools ranging ... Novell (via the Mono project). ...
    (microsoft.public.vb.general.discussion)
  • Re: Why .NET vs. Win32?
    ... It benefits the programmer and thereby the end user with more features, ... This advantage is of course much bigger for someone moving from say VB to ... VB.NET than someone moving from Delphi to Delphi.NET as Delphi has a good ... These are features of the programming language and environment ...
    (borland.public.delphi.non-technical)
  • Re: where do us long time VBers move on to?
    ... We're talking about the language here. ... objectives to the people. ... Delphi, ... >> It's not easy moving your code base, ...
    (microsoft.public.vb.general.discussion)