faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Status of khtml
by Thomas on Monday 30/Oct/2006, @10:07
|
Interesting this is...
> do unpaid work for Apple under their rules
I thought the appeal of unity is the other way round. KDE profits from further developments of the Safari-team inside Apple. It's supposed to be a win-win situation, as Apple does pay some developers to work on an OSS project...
I think the biggest argument speaking against unity is that khtml is elegant and does little compromises in terms of code cleanness and quality, whereas apples fork of khtml got some unattractive modifications (probably in quick'n'dirty style). It's the way software has to be done in the big business, but just not the usual style of an OSS project and especially not of KDE... |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Status of khtml
by Carewolf on Monday 30/Oct/2006, @13:54
|
That argument is a little dead now. Actually Apple are doing a lot to clean up the code and there are many ugly parts in KDE KHTML as well.
The problem is more that WebKit is still predominately developed for Safari, which means we either are forced to fork or follow Apple releases. Secondly that all patches has to be beneficial to Apple, because they can approve and disapprove patches, but not the other way around.
So the problem that needs to be resolved is some way to avoid being forcefed Apple dogfood.
|
[
Reply To This | View ]
|
Re: Status of khtml
by germain on Tuesday 31/Oct/2006, @16:16
|
> Actually Apple are doing a lot to clean up the code
As Nietzsche puts it "Who wears cleaned rags will be cleanly dressed without doubt, but dressed with rags nevertheless".
|
[
Reply To This | View ]
|
Re: Status of khtml
by germain on Tuesday 31/Oct/2006, @19:36
|
ouch! I forgot about the Nietzsche bot..
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|