Re: Does VCL have a future?
From: Dave Jewell (Dave.Jewell_at_btclick.com)
Date: 02/18/04
- Next message: Fritz Ulrich Cronen-Kämper: "Re: Retailing mythology"
- Previous message: Rudy Velthuis (TeamB): "Re: Delphi in Universities"
- In reply to: Xavier Pacheco (Xapware Technologies Inc.): "Re: Does VCL have a future?"
- Next in thread: Chris Burrows: "Re: Does VCL have a future?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 18 Feb 2004 11:15:55 -0000
"Xavier Pacheco (Xapware Technologies Inc.)" <xavier@xapwarespamless.com>
wrote
> Having written a book on both Delphi VCL and Delphi for .NET (primarily
focused on .NET, not VCL), I have concluded
> that the .NET framework (out of the box) is much richer in the
functionality it provides the developer than does the VCL
> framework (out of the box).
I'd certainly agree with this. Others have pointed out that it matters
whether you're comparing VCL.NET against WinForms or VCL.NET against the
whole FCL. It probably does matter for the sake of feature comparison, but
since parts of VCL.NET require FCL, it's probably not a meaningful issue.
> My suggestion is to learn the .NET framework as well as
> you know the VCL - than develop your own conclusion and go with it!
Again, I'd agree. I've always said that it benefits Delphi developers if
they have at least some understanding of the Win32 API. In the same way, it
makes sense for .NET developers to gain some familiarity with the FCL.
Dave
- Next message: Fritz Ulrich Cronen-Kämper: "Re: Retailing mythology"
- Previous message: Rudy Velthuis (TeamB): "Re: Delphi in Universities"
- In reply to: Xavier Pacheco (Xapware Technologies Inc.): "Re: Does VCL have a future?"
- Next in thread: Chris Burrows: "Re: Does VCL have a future?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|