On 24/11/2007, Giuliano Colla <[EMAIL PROTECTED]> wrote:
>
> My guess. Nobody knows, not even Codegear.
> They've become more and more dependent on marketing rather than on sound
> technical strategies.

Yeah, I'm so glad our company decided to move over to Free Pascal.
CodeGear looks like it is going nowhere slowly.  Maybe Delphi will
have the same fate as Kylix had. Borland silently moving it to the
Historic Products section on their website.  Did anybody actually
check if they haven't done that already?  :-)

<off-topic>
Borland should have pushed CLX and Kylix much harder than trying to
play the catch-up game with Microsoft and trying to compete in the
.NET world. Obviously Visual Studio will always support .NET better
than any other product!
</off-topic>

> If we scratch our heads better than them, and it appears to me that the
> process has already begun, we may end up with a better solution before
> they've made up their mind.

Now see, this is exactly where I foresee a problem!  We find a
solution before CodeGear does and then CodeGear does something totally
different. Where does Lazarus then stand with Delphi compatibility???

<ranting begins>
I think we should bin the whole idea of trying to be compatible and
let the LCL implement it's own features.  Trying to be compatible is
just holding Lazarus back!  Take the Lazarus IDE for example. It's
goal isn't to be Delphi IDE compatible and because of that we can be
creative and inventive, and look at what a awesome IDE we have! LCL on
the other hand has improved by leaps and bounds over the last few
years, but will always stand in the shadow of the VCL.  My 2c worth.
<ranting ends>


Regards,
  - Graeme -


_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/

_________________________________________________________________
     To unsubscribe: mail [EMAIL PROTECTED] with
                "unsubscribe" as the Subject
   archives at http://www.lazarus.freepascal.org/mailarchives

Reply via email to