faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Wow..
by Eric Laffoon on Saturday 11/Sep/2004, @14:17
|
> should KDE get rid of khtml + kjs?
No! This is exactly the kind of senseless prattle that we should avoid as somebody is bound to think it's inside information. I was hacking Quanta only a couple meters from Lars and Zack, and KHTML is Lars' baby, along with a few other developers. I don't see them ditching it, thankfully.
> Warning: uninformed user opinion below ;)
Yes indeed. And while everyone has a right to their opinions we should also recognize that it's generally better to direct things from informed opinions. ;-)
> 1. Gecko has much more exposure (even though there is Safari) and thus at least _some_ web developers pay attention to make their site compatible.
Neither has enough market share to make a difference, but together they approach significance. FYI it's W3C standards compliance that serious web developers (who are not just using FlunkPage) want. That's a compliance issue with CSS-2 mainly right now.
> 2. Reduce duplication of efforts. The OSS world would have only one major rendering engine.
Remember KHTML working great when Mozilla was at 0.8 and less and had egregious rendering errors and couldn't even show form buttons right among other things? Go look at www.w3c.org and read everything there (that should take about a year) and tell me that you want to trust everything to one rendering engine. If that logic worked why not use IE? One is what MS is about. Choice is what OSS is about.
> 3. IMHO Gecko is still a little more standards compliant.
Okay, a little, but not by much. Now look at the architecture. Why did Apple choose KHTML when their team members were involved with Mozilla even though it was slightly more compliant? The answer to that question is why dropping it is utterly nuts.
> 4. The most important part last: devs could spend more time improving KDE instead of working on khtml :-)
BZZT!!! News flash! KHTML is part of KDE. Flash number two... uninformed users _shouldn't_ decide what developers work on... In fact since they don't what's the point? It's interesting that people almost always offer opinions with no substantial basis but rarely ask questions to determine if the facts support their initial supposition.
Informed software decisions by developers based on their assessments is why OSS is growing so fast and producing such respected software. What has been the problem with commercial software? Bean counters, investors, cliche marketing types and clueless journalists have had too much input in direction and scheduling. Think about it. If you're infected with interest (which is how developers get hooked) then seek information. ;-) |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Wow..
by yeahright on Saturday 11/Sep/2004, @17:20
|
Lay off the coffee for a while, man.
|
[
Reply To This | View ]
|
Re: Wow..
by illogic-al on Sunday 12/Sep/2004, @19:24
|
indeed. He's more than allowed to give his opinion and If I read correctly, he actually changed his ming about some of the things he said after becoming informed.
See how much good can happen when you don't go off attacking those unfortunate enough to not know better and instead explaining in a calm manner?
|
[
Reply To This | View ]
|
Re: Wow..
by wg on Tuesday 14/Sep/2004, @00:53
|
Maybe Eric's post was a little harsh, but he is absolutely correct. Choice is a good thing. Competition is a good thing. We need to get away from the mentality that there can (or should) only be one product in any category. If you are a commercial software company it is in your best interest to try to kill off competing products until yours is the only one left. But, if you are a consumer/user it is in your best interest to encourage the existance of multiple competing products, even if you only use one of them. If only one product exists what will you do when you become unhappy with it?
Competition causes products to improve faster. It also keeps any one product from dictating standards or having too much control of a market. Do we really want to have one development team dictating the future of the web? That is what we have now with Microsoft and IE. Is anyone happy with the current situation we're in? I'm not.
It is good to have multiple competing browser engines. It helps keep the browser developers focused on supporting standards instead of trying to rule the world. It also keeps web designers from getting lazy and only supporting the dominant web browser.
By the way, Mozilla is my browser of choice. I only use Konqueror as a file manager and to test web pages. But I hope KHTML has a bright future. KHTML is important regardless of whether or not it is the number one browser engine or not.
|
[
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)
