faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Pleased with QtBrowser
by Iuri Fiedoruk on Wednesday 16/Apr/2008, @14:49
|
Well, yes and no.
You see, a lot of users did not wanted the dying of kicker, but it happened for better (at least we hope so). :)
But yes, I'm not saying khtml must die now, but webkit is the future, soon or later it will be one of the dominant engines.
Look at maemo, qt, safari, iPhone, android and you see a bright future for it. |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Pleased with QtBrowser
by Luca Beltrame on Wednesday 16/Apr/2008, @22:29
|
"You see, a lot of users did not wanted the dying of kicker, but it happened for better (at least we hope so). :)"
I'm sure you're well intentioned and aren't doing this in bad faith, but why, *every* time you post about Plasma, you take shots at it?
|
[
Reply To This | View ]
|
Re: Pleased with QtBrowser
by eds on Wednesday 16/Apr/2008, @22:50
|
He is a well known strong supporter of old good kicker and Webkit. He doesn't really like plasma (KDE 4.0.x version of plasma to be more precise) and really likes to discredit KHTML ;)
|
[
Reply To This | View ]
|
Re: Pleased with QtBrowser
by Iuri Fiedoruk on Thursday 17/Apr/2008, @05:39
|
Yes and no :)
Plasma 4.0 = trash, crash, poor, less than alfa-quality.
Plasma 4.1+ = gold, awesome, impressive, shiny.
I was not being sarcastic, I've already asked forgiveness to Aaron Seigo (and can ask how many time it is needed, he can ask me to do so as many times he wish, I don't mind), because I think his *vision* of plasma as substitute to the old desktop is right and plasmoids development will be more easy than creating a cake.
The problem is that plasma is far from ready now, and I won't even talk about way back when 4.0 was released.
The main idea of plasma was having a stable base where developers could create widgets without changes in the code each new kde version and that plasma updates could be distributed indepentent of KDE release cycles. I've asked Aaron, and he said this will happen on 4.1 and afterwards.
So, long history short: After KDE 4.1 plasma is the king, if they had released kde 4.0 as kde4-developer-edition I would have nothing to complain.
I just have strong opinions, as Aaron does.
Our last struggle was about removing those crappy mini-icons on plasmoids. He did not liked my (and other opinions) and we kind of crashed, but that does not mean I don't respect and admire him, I just won't help get his ego bigger because a big ego leads to bad decisions ;)
|
[
Reply To This | View ]
|
|
Re: Pleased with QtBrowser
by eds on Wednesday 16/Apr/2008, @22:39
|
Well, kicker died because all the developers have agreed that it must die, and porting all those kicker applets would be just waste of time. In the case of KHTML, none of KDE developers say KHTML shall die ;)
Well, we just see, whether KHTML will die as what you wish or it will still strive as an alternative rendering engine. With the introduction of KHTML in Windows, I'm sure KHTML will get more market share.
(And safari in Windows is not as good as Safari on Mac, I prefer Firefox over Safari in Windows, and if Konqueror has been stabilize on Windows, surely I'll use Konqueror)
Alternative is good, do you know even there are more smaller open source rendering engines which have smaller market share - even maybe less than 0.001% market share? Like Netsurf for RiscOS, which is quite capable despite it is still very young and ultra-lightweightness.
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
