Re: Is anything spectacular going to happen around Delphi anymore?

From: Rudy Velthuis [TeamB] (rvelthuis_at_gmx.de)
Date: 06/25/04 

Date: Fri, 25 Jun 2004 21:05:11 +0200

At 20:25:31, 25.06.2004, Serge Dosyukov (Dragon Soft) wrote:

> If I may make some correction to your statement
>
> > Now add to that, that
> > - you can keep on using the code you had written before, for Win32
>
> this is a "hype". DfN as an environment is not compatible with prior
> versions until you are using it just as a language and used something
> more then functionality of D1.

No, it is not hype. Any code not doing something too far out of the blue,
or using assembler, can easily be recompiled. Of course this assumes you
don't use a technology not available on .NET.

It helps if you had already adjusted your code using the D7 warnings, of
course. IME, I was most of the time able to refactor my platform
dependent code out into a few functions or classes, and implement these
differently depending on the CLR define.

> > - the VCL wraps the OS right now, and probably still does when Avalon
> > is the preferred base for .NET.
>
> DfN still uses a lot of win32 and even Borland admit it. In some areas
> this "wrapping" is from the past.

Oh, I agree that it will take time to port this, but it also took time to
port everything to .NET and to Linux. It should be getting easier all the
time.

> > me to see things from a distance. I do not fall for the FUD and hype
> > that seem to be the real problem on these groups.
>
> assumption?

As the word "seem" implies, right?
 
> > I think that much of these problems are perceived, and the notion is
> > not new either. Usually such problems arise when people expect
> > something, and don't see it implemented by Borland. This means they
> > start doubting Borland's sanity, and it makes them look for
> > alternatives.
>
> yes, expectations... people are developing in modern world wich did
> change a lot during past years since D7 release, even since DfN release.

I have no diea what that has to do with what i am saying. You should be
able to use new technlogies with existing Delphis (heck, most of the
newer technologies for Win32 could probably even be programmed in Delphi
5).

> > I always wondered why people would throw away everything they have
> > developed for years, just to be able to have that new feature, since
> > it is a must have, these days.
>
> Probably to be able to make new sales... to keep up with market
> requirements... etc.

Nonsense. There is usually no need to jump languages to do that. Now you
mentioned Unicode. Except for using C++ and plain API, how would you do
that for Win32?

And on .NET, it is a given. No need to move to C# or VB.NET. 

-- 
Rudy Velthuis [TeamB]
"There is more stupidity than hydrogen in the universe, and it has a
longer shelf life."
    - Frank Zappa

Relevant Pages

  • Re: Win32 and C++
    ... I am a newbie to Win32 and C++. ... The model in Windows, are simply too poorly engineered. ... most frameworks under Windows using C++ are poorly engineered. ... they make no distinction between the language proper and frameworks ...
    (microsoft.public.win32.programmer.ui)
  • Re: About speed
    ... | advantage is using a outer language to process text into internal ... The point that you are missing in this discussion is that Delphi for .NET is ... Programming for a managed environment is not the same as programming for a ... Unlike in Win32, .NET strings are immutable, you have to consider this ...
    (borland.public.delphi.non-technical)
  • Re: History of SSG and Symstream on 2200?
    ... advantages of Python. ... With the posting of the Windows port of SSG, I had thought it might be ... or indeed any other such scripting language ... So there is a "paradigm mismatch" between SSG and most modern scripting ...
    (comp.sys.unisys)
  • Why no language improvements?
    ... I would be doing a lot more delphi ... The language is almost identical to ... Win32 and Kylix releases, you could have eclipsed.net by ... A massive runtime that needs to be installed and even more massive ...
    (borland.public.delphi.non-technical)
  • Re: There is no market for a Delphi for .NET compiler
    ... Do you have a need for a Delphi for .NET compiler? ... Win32 for our development. ... that I know the language and don't want to start learning a new language for ... for the .Net developers. ...
    (borland.public.delphi.non-technical)
Loading