Quote
>This at least is what I'd like to see, and Borlands decision to drop
>the CLX for Windows by no means is a road-block for that.
>
>Simon
>
CLX is the only framework Kylix has, so if Borland is no longer
actively working on that, it's not a good sign.
This doesn't make any sense. Kylix has any framework you compile
with it.
The question also is what you personally think Kylix is.
My impression on the various aspects is the following:
1.) The CLX.
The CLX more or less is just a renamed VCL clone. The Windows part of it doesn't
have any future. Nobody likes the drawback of working non-native under Windows.
The Linux part of it actively maintained by the FreeCLX project now. For Linux it
will stay and get updated. In the future, the CLX hopefully will become so compatible
to the VCL that visually you can't spot a difference for the components. This will
allow you to use the VCL Form Designer, which is actively maintained by Borland.
2.) The Kylix IDE
As you may know, Delphi 2000 uses the Galileo IDE, which is a complete rewrite. The
Kylix IDE is based on the old Delphi 6/7 IDE. That makes the current Kylix IDE a
pretty much dead-end. I don't expect a new Kylix IDE for the near future. If Borland
again sees a market for a Linux IDE, they might one day do another attempt. I
personally don't expect a new Kylix IDE for the near future.
3.) The compiler
The Kylix compiler works like a charm. Also it should be easily updateable to the
current state of the Win32 compiler. It would be a rather small investment for Borland
to get their customers an updated Kylix compiler.
4.) Cross-Platform development Windows/Linux
In my personal, very biased opinion, "Kylix" has a bright future here. All that's needed
to make Delphi a perfect cross-platform RAD solution is:
a) A crosscompiler integrated into the Delphi IDE. The Delphi 2005 IDE is perfectly
extendable in this area due to its "personality" support. And as a temporary solution,
we currently have CrossKylix.
b) A cross-platform GUI framework. VCL on Windows + "CLX" for Linux will provide this.
That's the way quite a few people have used Delphi/Kylix from the start anyway, using
some IFDEFs.
c) A remote de{*word*81}.
Summary:
If you are a Linux developer, who wants to develop only under Linux and for Linux, forget
about Kylix. Most "real Linux geeks" don't want RAD, but {*word*155} low-level c. Near all
of them don't want to work with closed-source software, and even less want to pay money
for software. That's the reality Borland has faced when trying to sell Kylix.
If you are a Windows developer who also wants to deploy some of this applications to Linux,
then you can safely stay with Kylix. Right now writing all kind of web services, server-,
database and middleware applications works like a charme without any real issues, and
you can enjoy the full RAD power of Delphi. And if you are more into GUI client
applications, you currently have to work around some compatibility issues and bugs, but
it works, and chances are good it will get much better soon.
I personally think that 99% of all people that paid for Kylix are Users coming from the
Delphi Windows world. From a business standpoint it would totally make sense to keep
these customers.
Personally I would not miss the Kylix IDE at all. I never used it. I always created
my Applications under Windows and then compiled them on Linux. I have the feeling I'm
not alone. The number of CrossKylix users points into the same direction.
My personal hope is that Borland will integrate everything needed to build Linux
applications into the Delphi IDE.
Simon