decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Yep, Miguel | 234 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Yep, Miguel
Authored by: odysseus on Monday, November 12 2012 @ 08:56 AM EST
As I pointed out at the time, what Miguel talked about was almost entirely a
problem with Gnome, not Qt/KDE. On the Q/K side of things we strive very hard
to maintain backwards compatibility and support the full set of API's throughout
each major release cycle. That's an inheritance from Qt's commercial roots with
paying customers to keep happy, and one reason we have so many abstraction
layers implemented, they isolate our developers from the underlying system
changes meaning we can guarantee compatibility and support. It was Gnome that
played fast and loose with dependencies and release numbering and annoyed the
devs, but in Miguel's world that equals the Linux Desktop.

It's interesting that the article mentions both Gnome and KDE being wrong on
CORBA, as Miguel doesn't mention it in his blog, and he wouldn't as KDE was
actually right about it. Gnome wanted to use CORBA for IPC and tried to talk
KDE into using it too as a common IPC would make sense. KDE looked at it,
decided it was far too heavy and technically unfeasible so built their own
light-weight version called DCOP which proved a success, where-as Gnome's
implementation called Bonobo was always a problem. When Gnome realised this,
rather than adopt or adapt DCOP directly (as it was KDE stuff and so
unaccepatble for mostly political reasons), they created DBUS based heavily on
DCOP but fully re-implemented it with a number of unfortunate short-comings.
With KDE4, rather than continue with this split KDE agreed to adopt DBUS for IPC
as well, but we miss the features we had to give up like network transparency.
OK, at least that's my KDE-biased recollection of it, Gnome might see it
different.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )