[news.eclipse.tools] Re: KDE and GNOME interfaces

[David Goodenough <david.goodenough@xxxxxxxxxxxxx>]

McQ wrote:

> 
> "Scott Stanchfield" <thetick@xxxxxxxxxxxx> wrote in message
> news:9lgsad$ge5$1@xxxxxxxxxxxxxxxx
>> Actually, I think they'd still need to build an API on top of that so
>> they have their own API that our apps could use that would workon any
>> platform.
>>
> This is exactly the case. From our point of view, it wasn't clear that
> adding the dependency on the kde java binding added sufficient value
> versus just doing it in C natives (some flavor of which we had to write on
> other platforms anyway).
> 
> McQ.

The value is consistancy, we (the users) only have to learn one API and
we do not have to worry about level dependancies as the KDE provided 
java binding will always be in step with the KDE that it is shipped with.

This, along with the whole SWT thing, is just making things complicated
for complication sake.  The transitory benefits are just not worth it.

In the film Amadeus, there was one scene which was historically acurate,
that in which the Emperor said that the problem with Mozarts Opera
was that there were too many notes.  Too many APIs is a real problem,
and to judge by the platform dependancies that are begining to show
between the Windows SWT and the Linux one this approach is going to
backfire.  I do wish IBM would reconsider.