faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Pleased with QtBrowser
by blauzahl on Thursday 17/Apr/2008, @10:05
|
> He didn't demand that they drop it immediately or anything like that.
He sure implies they might as well.
> Josep already posted some good reasons why.
He didn't post good reasons. He posted poor reasons, and he didn't even bother trying the most recent version of Konqueror to compare. Instead he implies it is so buggy he couldn't even get it to work. It works just fine for me, so if he's having problems, he should be filing bugs.
> By definition, you can't drop something that isn't actively developed, so using the fact that it is actively developed as a reason to not drop something is circular logic.
I'd like to point out that khtml is still under active development. Look at the changelogs for the 4.0.x releases. It's also pretty stable: in all the time I've played with 4, I've only crashed Konq once, and once I reported it, it was fixed within the day. |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Pleased with QtBrowser
by Jim on Thursday 17/Apr/2008, @11:00
|
> > He didn't demand that they drop it immediately or anything like that.
> He sure implies they might as well.
No, he didn't. Saying something "is the future" is *explicitly* making a statement not about the present, but the future.
> > Josep already posted some good reasons why.
> He didn't post good reasons.
Fast startup, fast rendering, really simple, very easy to use... they sound like decent reasons to me.
> he didn't even bother trying the most recent version of Konqueror to compare.
Would that be the version of Konqueror tied to the version of KDE that end-users have been told *time and time again* to stay away from because it isn't finished yet? Are you surprised that people are actually taking this advice?
> if he's having problems, he should be filing bugs.
No, if he's having problems, then that justifies his preference for another browser. You can't blame users for choosing a more stable competitor instead of helping you track down bugs.
> I'd like to point out that khtml is still under active development.
I wasn't saying otherwise. I was pointing out that isn't a reason not to drop it.
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|