Re: News from DevExpress

Per Bakkendorff wrote:
I don't agree. Delphi is widely used in native development, but if third
party vendors - such as DevExpress - drops Delphi, and only create new
components for .NET, then Delphi/CodeGear need to play catch up with
third party components, but they have to do it themselves!

Here are the facts:

1) DevExpress has already determined that it will no longer support
VCL.NET.
2) DevExpress is *not* dropping support for VCL.
3) DevExpress WinForms designers are custom built for VS.NET; CodeGear
appears to be dropping WinForms support.

So unless CodeGear picks up WinForms support again and DevExpress
decides to build designers for Delphi, how will anything change if
CodeGear dumps .NET altogether?

Julian points out that the Unicode support that comes, probably will
break the current VCL release of their components. If that market is
small, compared to their .NET market, do you think they will port their
components ? So when we have Unicode support, you don't have third party
components - where does that leave native development ? Would you
upgrade if the old code were lost ? I wouldn't !

If there is money to be made, someone will support the VCL. The key is
to make it large enough so that money can be made.

If CodeGear enhances the VCL, it is more likely this market will get
larger. If they neglect the VCL, this market will likely shrink. It's
as simple as that.

Besides, DevExpress has a vested interest in growing its VCL market as well.

Native development is important at this time yes, but in another thread
I read that other developers think that .NET development in Delphi is
important, if Delphi is to have a future. I tend to agree.

IMO, it's a question of "how" not "if". As it is today, .NET support in
Delphi is out of date and inferior.

--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.

Relevant Pages

  • My thoughts about Delphi and its future
    ... I only mention the Pascal part of Delphi because ... Cross-platform support. ... VCL framework is in my opinion the single most ... UI controls haven't changed since the beginning. ...
    (borland.public.delphi.non-technical)
  • Re: Captain Jakes Top Ten List of what Id like to see in thenextversionofDelphi
    ... Does DevExpress have VCL.NET components? ... VCL.NET they had received with VCL. ... And if you have a mountain of legacy Delphi code, ... God help us all if DevCo decides to let Microsoft dictate rich UI ...
    (borland.public.delphi.non-technical)
  • Re: Help to choose a BIG pack: TMS Subscription or DevExpress Subscription?
    ... DevExpress abandons all the VCL business and focuses on .NET only. ... We are not abandoning the VCL ... Unicode support, we'll be converting our own code to support it. ... Author of "Tomes of Delphi: ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Rich Client Applications and Codegears Strategy
    ... I'm 4 years VCL ... They are not spending any resources even for sample applications. ... (Devexpress, Telrik, ComponentOne, Infagistics, ... Just because there are no examples for Delphi doesn't force you to use ...
    (borland.public.delphi.non-technical)
  • Re: Delphi 2006 Feature Matrix
    ... Microsoft has nothing like VCL for unmanaged applications. ... that you can build reall production apps with Delphi ... > support, during a period where the Sun JDK 1.5 was still officially ... > All in all, I always have lately the impression, that the choosen release ...
    (borland.public.delphi.non-technical)