Firefox Lead Engineer Scolds KDE Project 669
trent42 writes "Firefox lead developer Ben Goodger has had harsh words on his blog for the KDE project, in light of its public tiff with Apple over the KHTML rendering engine. Goodger says 'Safari's renderer is vastly superior to the KHTML used by Konqueror,' and that the KDE developers should follow Apple's lead and focus more on the needs of users, instead of insisting on software perfection."
Agile (Score:3, Insightful)
Re:Agile (Score:5, Interesting)
Remember what it was like before Agile? Companies and consultants would develop big blocks of software, check it in, QA it, and show the customer who'd get pissy because it didn't work the way they expected. Yes, Agile prevents that. But seeing what is happening, I'd say that KDE does is very Agile, unlike what Apple just did.
Oz
Tests are no substitute for good design (Score:5, Insightful)
I am sure to be modded OT as this whole thread is, but...
The Agile/XP movement is warped at best. Tests are no substitute for good design and they cannot prove any useful level conformance to a design (except in an extremely trivial application). Tests are useful in many cases, unless they are used to rationalize bad practices based on false notions.
And the more extremists you have trying to force it to be so, the worse the XP/Agile movement is percieved. Sure, they picked up on parts of a number of good practices that good programmers already followed, but when will they stop twisting them and advocating that experienced programmers abandon principles of adequate forward-looking design and methodology and follow the way which is what they ultimately believe to be The Only Right Extreme Way.
They resemble the pointy-haired managers who would like to think they can substitute their process for masterful programming and design.
I was attracted to XP by their advocacy of some of the more-reasonable principles until the fanatics showed why it was really called extreme programming. They need apologists to start really apologizing.
Re:Tests are no substitute for good design (Score:3, Insightful)
Unit tests (written with frameworks like JUnit or TestNG) are intended to require a perspective shift of the developer writing the code. Specifically, the developer must think like a client programmer for whatever module they are testing. As such, these kinds of tests are design aids, not design replacements. In fact, they are advocated not for their ability to verify requirements, but rather, for their ability make design improvement less risky.
Naturally, accepting this requires a reasonable adjustment
Re:Tests are no substitute for good design (Score:3, Insightful)
In other words - carry on the way you were. Is it really such a revolution to say "don't do unnecessary work?"
Why, thank you! I'd never thought of that. If you're "in a project where you can go ahead successfully without performing an initial design phase," then you're probably working on Hello World.
Really, the secret is hire good people to do the job, set realistic deadlines but enforce them, block
The XP "methodology" works for evolving things like GUIs and little el
Re:Agile (Score:3, Informative)
Apple sells hardware. KDE is a developer-first focus. They profit stricly on developer sales. Not hardware, sales, as Apple ..
I'm not 100% certain, but I *think* Apple sells software, too. Stuff like OS X, iWork, Final Cut Pro, DVD Studio Pro, Motion, iLife, WebObjects, Shake. From all evidence that I can see, that's software.
Re:Agile (Score:5, Insightful)
Direct software sales may only be 4%, but software is a much larger part of their business than just the revenue percentages indicate.
Re:Agile (Score:3, Interesting)
It is interesting that Apple's policy of giving away software - principally OS X - to sell hardware means that from an investment analyst's viewpoint the company's stock is expected to have a much lower P/E than if it sold the software separately. Companies that sell software can have huge P/E ratios.
Re:??? HUH ??? (Score:3, Insightful)
Martin Fowler has tremendous insight, which is not to say we should swallow Agile Development or XP whole, but rather look to the New Methodology for ways to improve.
Your article mentions looking to government and large corporations for the answers about the Right way to program. I suppose it refers to someone like Microsoft, who has no real notion of unit testing in their software development process?
Th
Re:??? HUH ??? (Score:3, Interesting)
Agile works as long as the customer is willing to pay for the changes. Agile is good because the customer sees progress. Agile is bad because an indecisive customer can flip-flop on features and cause significant headaches.
Fragile works better where the customer needs a specific solution. The
Can't wait... (Score:3, Insightful)
Personally I can't wait for the KDE response which scolds the Firefox developers for having such huge and stupid security holes in their browser.
Maybe the Firefox team should get rid of the glass walls before they start chucking stones at other people.
Re:Can't wait... (Score:5, Interesting)
I actually like the KDE browser better than Firefox. I love the built in spell check and it is fast.
But I can not use it with Google maps or the full version of gmail.
Has Safari introduced any huge security holes? The latest Firefox hole seemed less that huge to me. Yes it could be exploited by a white listed site but the only white listed site I have is Mozilla.org
It was also patched very quickly.
Re:Can't wait... (Score:3, Informative)
Javascript itself has been standardized by the ECMA as ECMA-262 (ECMAScript) ever since Netscape donated the language to said ECMA (even though ECMA's work blows and no one ever read the normative definition because it sucks donkey balls), and W3C's DOM and DOM Events have extensive documentations [u]including documentations on how you're supposed to implement ECMAScript bindings[/u].
And that's not to mention really good reference sites such as QuirksMode [quirksmode.org], which is
Re:Can't wait... (Score:3, Interesting)
Are the editors just doing this for kicks? I have to admit, I've gotten sucked in and made the comments too.
First, we get repeated Evolution vs Intelligent Design debates until everyone was sick of them. Now, its the Apple/KDE. Maybe after a week we'll get ad naseum:
Apple rocks/sucks
Linux vs Windows
Java vs world
OOo using java
Your favorite open source product has new security hole
Your most hated closed source product has security hole
wha, I j
Re:Can't wait... (Score:3, Insightful)
Re:Can't wait... (Score:3, Insightful)
I guess there aren't any remaining holes in Apache, Samba, or Cups, because the all powerful Apple is bundling them with OS X.
In a way I agree (Score:5, Insightful)
In a way, I agree. It's comforting to sit down, load an app, and have everything work. Knowing it's not quite perfectly written behind the scenes is a small worry sitting in the back of my mind, but it's smaller than when I have a slightly clumsy app that is otherwise technically correct.
Not that I think Konq is all that far behind in the user side of things.
Re:In a way I agree (Score:3, Insightful)
Ok, so that sounds like IE's early days. I say "early days" because its flaws are nothing less than eyepopping these days. Anyway, I don't care how well Safari works and how good or bad it is or isn't behind the scenes. What I care for is that Konqueror is very well written, very stable and very fast. I use Konqueror (for browsing) about as much as Firefox, maybe more. I really think the Konqueror guy
Re:In a way I agree (Score:5, Insightful)
The patches submitted back to KHTML may be harder to integrated more because the changes made to Safari are greater and in a different direction than KHTML.
I think there is a bit of arrogance on the KHTML side to not even consider the aspect of WebCore.
The holier than thou attitude seems very pervasive in the Open Source Community. It's not unlike the Not Invented Here syndrome that many corporations suffer from.
Apple is offering up their changes but seem to have said "We've made major improvements that can't easily be patched in to the existing base. We offer the opportunity to use this new code as a basis for the future."
Re:In a way I agree (Score:4, Funny)
Re:In a way I agree (Score:4, Interesting)
Slow down cowboy, I think you are talking about SCO here, not Apple! Someone creating a new project based on your free code is a compliment, not a stab in the back. KDE developers should just take any portion of Apple's changes they find useful and let the rest stay in a separate project. If later Apple wants to take advantage of improvements in the new version of KHTML, they will then do the work of integrating their own dirty patches without any prodding.
In the meantime, the rest of us can hope for a GNUStep webcore-based browser and saying goodbye to bloated Linux desktop environments that try to look like Windows.
Re:In a way I agree (Score:4, Insightful)
You know that if something renders in Mozilla, it'll probably work in Firefox, Galeon, Netscape, etc. This is great for both web developers and the browser teams, as it reduces the amount of testing needed (it especially helps the little-known Gecko-based projects that would never get tested against themselves). The KDE project could benefit hugely from having a truly shared HTML rendering core with Safari, as large developers such as Google already make their pages avaiable in Safari but not Konqueror. Fragmenting KHTML/WebCore only makes both less useful to test against, though this hurts KDE much more than Apple.
Apple offered, but KHTML didn't want to. (Score:5, Insightful)
The KHTML team turned them down. They probably did so because it would shift the focus away from the KHTML they know and love and more towards the more realistic (but messier) WebCore, which they don't seem to want to do.
The KHTML team doesn't even seem to want many of the changes. Apple makes a product, and they don't care if they break small things to make deadlines. KHTML is a product of the opposite school, preferring to make a very small, clean codebase. The price of this is feature deficit.
This isn't about Apple being evil, or KHTML being snobs. It's about a project being forked. As time goes on, Apple has less and less to offer to KHTML. WebCore and KHTML are diverging, and people seem to be upset about this. I can't imagine why, this sort of separation was inevitable. Apple's best interests are served by leveraging their own excellent environment, and every time they do, they further exclude the KDE project.
Don't Follow Firefox Adivce: considered Bad! (Score:3, Insightful)
Re:Don't Follow Firefox Adivce: considered Bad! (Score:3, Interesting)
The "wisdom" of that choice has forced them to rebuild market share from scratch -- from 0% -- because the 60-some percent of people who were using Netscape when they started had completely bled away by the time they were done.
Don't get me wrong, I loooove what Firefox has become. But I would hardly point to the early management decisions of the Mozilla Project as a shining example of the Right Way to do software.
Re:In a way I agree (Score:5, Insightful)
Ok, so that sounds like IE's early days. I say "early days" because its flaws are nothing less than eyepopping these days. Anyway, I don't care how well Safari works and how good or bad it is or isn't behind the scenes. What I care for is that Konqueror is very well written, very stable and very fast. I use Konqueror (for browsing) about as much as Firefox, maybe more. I really think the Konqueror guys deserve every bit of appreciation for their long great work. I wouldn't like KHTML being dropped in favour of an engine hacked together by Apple devs.
I think you're missing the bigger point here....
Yes, KHTML is "well written, very stable and very fast". But so is WebCore, which is obviously derived from the same KHTML tree that you care for so deeply... but WebCore is vastly more capable. Sure, the KHTML guys deserve recoginition for their work, but to characterize Apple's fork as "hacked together" is a gross misunderstanding. The WebCore engine is clearly the superior technology and Apple's developers are clearly responsible for the progression that WebCore has made over KHTML.
The reality here is that this whole mess is nothing more than KHTML's developers wanting to have their cake and eat it to. They welcomed Apple to the table with the hopes of some full time developers helping out with KHTML, but then poo-poo'd Apple's efforts when they realised that Apple was foolishly committed to solving problems for their customers, rather then just writing pretty code.
This is one of those problems that happens time and time agian with open source projects - the developers become so consumed by making a technically superior product that they forget to deal with the fact that it's functionally underwhelming. There are a choice few exceptions to this rule... great sucess stories no doubt (Linux and Apache come to mind)... but they are certainly the exception, not the rule. Case in point... the Gimp. If I hear one more zealot even try to compare it to Photoshop.... No doubt, the code to the Gimp is probably cleaner,better written, and less prone to memory leaks.... but it doesn't change the fact that Photoshop is light years more advanced (4 letters: CMYK) and a lot more elegent to use.
Of course, what really bothers me is when these inadequecies are overlooked by zealots who disregard ease-of-use and functional elegence because they appreciate the idealogy of the developers. What kind of brain-dead reasoning is that? If "poorly" designed code -works better- for the end user, than it's not so poor afterall. This is the key point the KHTML people have missed.
At the end of the day... If the Konq guys absorbed Apple's changes, rather than crying about them, you certaintly wouldn't be complaining that suddenly Konq was a whole lot better than it was -before- Apple got involved, now would you?
Re:In a way I agree (Score:3, Interesting)
This argument made more sense 3 years ago. Then K
Re:In a way I agree (Score:3, Informative)
it has the panther, tiger and something else themes
Re:In a way I agree (Score:5, Insightful)
I think one of the strengths of Open Source is that developers are not under economic presure to deliver it yesterday. They have usually taken the approach of getting it right. I think this means products are sometimes longer to market, but its a trade off. Its one that can be made in open source, but isn't always availible to a commercial developer, they often need code now, correct or not.
Re:In a way I agree (Score:3, Interesting)
KDE's infrastructure allows for a modern, well-integrated desktop. It is an example of object oriented principles being properly applied in real world development. Everything is richly context sensitive and there is a high degree of code modularity and re-use. To give a specific example, application file dialog widgets in KDE use the same objects as the Konqueror file manager component. Un
Expanding on parent a bit (Score:3, Insightful)
Opera.. [Yes damnit I'm mentioning Opera to be made an example of in an Apple-KHTML-Firefox related article so mod me offtopic if you must] manages a smooth, sexy well refined, suite with distinct lack of clumsiness, a fast and obviously efficient backend, with excellent standards compliance and features. You can almost taste the oodles of care put in to perfecting the product f
Take Notes (Score:4, Funny)
Re:Take Notes (Score:5, Funny)
Comment removed (Score:5, Funny)
Ben Goodger's blog URL (Score:4, Informative)
Uh.. (Score:4, Insightful)
Can't we figure out what the users need, and then deliver excellently written software to do that?
Re:Uh.. (Score:3, Insightful)
No, they're not, but they often can't be achieved in the same (usually all too brief) time frame. I tend to side with the Apple / Firefox folks on this argument -- fix it first, clean the code second.
It's interesting to note that Apple doesn't seem to have gotten into any significant disagreements with any of the other OSS people they're working with (regarding Darwin, etc.) along the lines of what's happening now with the KDE kamp. That leads a little more credence to Apple now, too.
Re:Uh.. (Score:4, Insightful)
Re:Uh.. (Score:5, Insightful)
Assuming you know the right way the first time you do something. Software isn't static, and nearly all requirements are fluid. By the time it's done right the requirements have changed and what you've done is no longer what's needed.
Re:Uh.. (Score:5, Interesting)
For all that has been said about a feud between KDE and Apple, the real feud is between the KDE developers and the users and slashbots who think that any new features in Safari should be in KDE too, and if they aren't it's because the KDE developers are slow, lazy, whatever.
It's worth noting that (from what I've heard, at least) the other open source projects that apple has used code from haven't gotten back much more in the way of useful contributions than the KDE team has.
Re:Uh.. (Score:5, Insightful)
It can be developed quickly, cheaply, or correctly (but you may only pick two of the three options)
Re:Uh.. (Score:4, Interesting)
This is not quite that software dilemma. Lifting something quoted in an earlier post:
"the KDE developers should follow Apple's lead and focus more on the needs of users, instead of insisting on software perfection."
This is about writing something that is correct to spec by the design document (i.e. the needs of the user--or maybe it is about getting the design document right?) vs. technically correct (i.e. perfect software--correct to the language spec, elegant, robust, no flaws, easily readable and maintainable, etc.)
Ideally, one's software would be both of these, and thus fit in the third category "correct".
I therefore propose that this old adage be modified thus: "On schedule, on budget, on spec, or few flaws--pick two"
Feel free to change those words to make it flow better. OT: in my limited experience, the scope of the project is always changing, so really none of those apply, therefore one can only really try to achieve #4, as few flaws as possible in what actually does get done.
Re:Uh.. (Score:3, Insightful)
Yes, yes, of course. No one has said "here's a good idea: write crappy code!"
The point is that writing code that is "good enough" should be balanced against giving your users a product which is "good enough" for their needs, and until it is, you should not focus on making the code "perfect" to the exclusion of things like meeting release dates; issuing bug-fixes; etc.
Balance in all things, and when in doubt, favor the user. That's all that's bei
User Needs vs Software Perfection (Score:4, Insightful)
Now I think back to 1995, when IE focused on user needs over software perfection and the following of published specifications. And look what a mess of incompatibility we have today of javascript, css, java VMs, etc. Mainly because M$ focused on 'the needs of users.' No thanks, I'll stick to the specs.
Re:User Needs vs Software Perfection (Score:5, Insightful)
Utter nonsense. I too can think back to those days, and no browser was following the specs. "Netscape is the next Microsoft" was a common complaint, as Netscape piled proprietary tag after proprietary tag into their browser. And don't even think about their initial CSS stab, the web still suffers from that today.
Cheers,
Ian
Re:User Needs vs Software Perfection (Score:3, Interesting)
And don't even think about their initial CSS stab, the web still suffers from that today.
Practically everybody has dropped Netscape 4 support by now.
Their "initial CSS stab" was a rushed job. They had decided that JSSSL, a stylesheet language based on Javascript, was a better choice than CSS. The W3C decided to adopt CSS rather than JSSSL, and so they had to back-pedal and add support for CSS quickly.
Interestingly enough, one of the big criticisms of JSSSL is that it violated the "Principle of L
Re:User Needs vs Software Perfection (Score:3, Insightful)
I agree with the original poster's implication that sticking to the specifications is better than attending to the needs of users. The ISO and ANSI committees exist for a reason: when new features need to be added to an existing specification, the committees consider them and update the specification so that all implementers of the specification can do what's "best for the user" at the same time.
Granted, I'm living in a
Re:User Needs vs Software Perfection (Score:5, Insightful)
Re:User Needs vs Software Perfection (Score:3, Informative)
Re:User Needs vs Software Perfection (Score:4, Insightful)
Safari's code is capable of performing to publish specifications.
Microsoft's objective was to create their own specification.
Entirely different thinking.
Re:User Needs vs Software Perfection (Score:5, Informative)
2- You probably missed all the proprietary MS crap in their implementation of the CSS, such as scollbar shit, that was NOT implemented in a W3C-compliant style (W3C allows proprietary CSS properties, but you HAVE to use precise prefix of type "-name-", which is why you see such things as -moz-outline)
3- CSS in IE6 is not "kinda bad", it's an awful heap of crap and a pain to work with from a dev's point of view
4- And if we extend from W3C's CSS to W3C's everything, MSIE sucks at W3C's HTML (heaps of missing tags, or not completely implemented ones), XHTML (which it doesn't understand at all in fact), W3C DOM/DOM Events and their binding in ECMA-262 (also known as ECMAScript/Javascript), XSL/XSLT...
Re:User Needs vs Software Perfection (Score:4, Informative)
They are saying that, despite all the media to the contrary, Apple's work is of no use to the KHTML developers. This is because Apple has been providing its changes in huge blobs without providing any clues what those changes are for or how they relate the the rest of the KHTML renderer.
Apple is following the license, which was never in doubt, but is being mean-spirited about it. The KDE devs just want people to stop the nonsensical meme that Apple is somehow helping KHTML development.
As I understand the situation, it is somewhat like an editor of a large book returning to the author only the errors in the book, but without any type of markup or explanation, in no particular order, and in a foreign language the author doesn't know. While the editor was (strictly speaking) doing his job (which is to find the errors in the book), he wasn't being very helpful.
The code could be sorted out, given enough time, but it's just as productive to ignore Apple's changes and do it from scratch.
This has nothing to do with focusing on the needs of the users, and it has nothing to do with software perfection. It is purely an issue of Apple being credited with helping KHTML, when it is doing nothing of the sort.
Re:Boy are you dumb (Score:4, Interesting)
I'm not saying that this is a bad thing, in fact it's an excellent thing. But the fact is Safari, Mozilla and MSIE all failed the Acid 2 test when it was released. Using MSIE I see red. lol.
Now Safari passes. And no doubt each would fail several more tough tests. No one test can prove a superior rendering engine, unless it was 10 MB big and tested every [X]HTML/CSS1,2,3/JavaScript specification in various scenarios.
I'm looking foward to getting a Mac Mini and seing how good Safari is. It will also allow me to develop web pages against Safari for the first time.
Re:Boy are you dumb (Score:4, Interesting)
Wasn't that the purpose of the Acid 2 test? To give an example of common rendering problems so that browser developers could see what their browser was doing wrong? Now, I'm not saying that passing the Acid2 test means the rendering is perfect, but the challenge was placed out there, and the Safari developers took it up. It's exactly what Mozilla and MS and KDE should do, too.
Now, if after all that, we can come up with a new series of serious rendering errors not addressed by the Acid2 test, then let's make an Acid3 test, or whatever. But I don't see the grounds for complaint. It's like saying, "well the only reason Firefox renders HTML properly is because the Mozilla team spent time to make it render HTML properly." Well, good. That's what they should be doing.
Oh holy shit (Score:5, Insightful)
Re:Oh holy shit (Score:3, Funny)
Well, he started it!!
Seriously, the occasional blow-up like this is probably good in the long run. If a little embarassing to watch now.
Heh... (Score:5, Insightful)
I got on the KDE guys for their bit yesterday, so today I'll point out to the Mozilla side that the reason there was a decent browser for Linux in 1999 was that the Konqueror guys satisfied the needs of users while Mozilla went off constructing a whole new software platform...
Re:Heh... (Score:3, Interesting)
In the short term, a hack will get a feature out the door more quickly. In the long term, a pile of hacks doesn't hold up as well as a properly engineered soltution. Notice how some browsers (Netscape, ie) had to be rewritten from scratch a few times.
It seems to me that each project shou
Re:Heh... (Score:3, Interesting)
I hope so. I've found bugs in Safari's rendering which aren't in recent Konqueror releases - one I've seen a lot involves CSS-defined borders on table cells creeping out from where they're supposed to be.
Here's a rather nasty example [hylobatidae.org] I've plucked from a site I've worked on - excuse the awful HTML!
On Safari 1.3 on MacOS X 10.3.9,
Mutually Exclusive? (Score:3, Interesting)
"The KDE developers should follow Apple's lead and focus more on the needs of users, instead of insisting on software perfection."
Are these two things really mutually exclusive?
Re:Mutually Exclusive? (Score:4, Insightful)
I guess that makes the assumption that the needs of the users includes a rapidly expanding feature set and whatnot. And while that is important (particularly if you're going for marketshare), there are still users who'd rather have some good code. Not to mention that eventually the bad code may catch up to you, and cause the needs of the users to change. Windows needed a lot of usability enhancements until the Win95-98 era. Then stability became a big issue. MS ironed a lot of those problems out, and now security and spyware is the big problem. A lot of those issues could have been mitigated by better code at earlier stages. Fortunately for MS, their monopoly has allowed them to advertise their security and spyware solutions as new features, and so a mostly under-informed public still thinks they're paying for innovative work.
But returning to the original point, even for a big, well funded company like MS or Apple, it's not really possible to write perfect software fast enough to lead the market in features. You can dump more money into it, and hire more engineers, but that just makes it all the more complicated and harder to coordinate, leading to more mistakes.
The KHTML team can avoid that because they're not trying to keep a business profitable, they're writing this stuff because it's a hobby for them. Personally, I try and keep my hobbies as free of deadlines as is possible. And if anyone wants to criticize how I indulge in my hobbies in any sort of non-constructive way, they can go to hell, I'm not interested.
Is it tortoise and the hare? (Score:3, Insightful)
Evenutally, that hack becomes a trouble to maintain and I'd bet my bottom dollar that it then takes more time to remove the hack and rework it properly that it would have taken to fix it properly in the first place.
I suspect the reason Longhorn is taking so damned long is because this problem is just starting to pinch Microsoft. The "Just get the product out" mentality works for a while - but then all that extra complexity comes back and makes your life very hard.
Simon.
Pissing contests (Score:5, Insightful)
Here we have several very adept programmers slapping at one another over how their respective web browsers work. Am I the only one out there that finds this kind of bickering trivial and unproductive?
Yes, people will have disagreements, and people will have different ways of doing things. Fine. But why not harness those different perspectives and create something better?
As long as OSS projects are afflicted by this kind of petty squabbling, developers' attention will be diverted from creating quality software. Now knock it off!
Re:Pissing contests (Score:5, Insightful)
Konq vs FireFox vs world (Score:4, Interesting)
As a general web-browser I find Konq to be slow and kludgy, but it has never dissappointed me on the stubborn sites.
Anybody found similar situations?
Re:Konq vs FireFox vs world (Score:3, Informative)
Odd.. (Score:5, Insightful)
And guess what KHTML's team is? That's right. Full of software engineers. Which is why they care.
Secondly, developers should prioritise releasing their products on time, even if they "may have to cut corners".
Software developers in the open-source world make software because they love to. They want to make their project (note: not product) the best it can be. Releasing products on time is straight from the Marketing Department.
Goodger has every right to give an opinion, but no right to flame others for caring about their projects, much like Mozilla used to, before they gave up a large part of their community.
Love for a project, not releasing products in a timely fashion is what makes open-source different, and much appreciated.
Re:Odd.. (Score:3, Insightful)
Maybe the code itself, the creation of a tight, well written, efficient bundle of code is the target. They aren't doing it to fill an opening in the market, they're doing it for the love of the game.
And in the process, they made something that a company as in
No shit Einstein! (Score:5, Insightful)
Isn't that exactly what the KDE-developers said?? Sheesh!
I for one think that it's great that there are still people out there with a goal to create perfect code, and not just slap features together. It's interesting that Apple chose KHTML because the code was clean, fast and small. And now this guys suggests that KDE abandons those benefits and moves to Webcore (which has lost most of those benefits due to cutting corners and less than perfect code).
Is that it? Crummy code that is "good enough" is the way to go?
That just doesn't sound right (Score:5, Insightful)
I can't say I feel comfortable hearing that type of reasoning coming from a Lead Engineer of my favourite web browser. I'm not a Microsoft fan but if an IE developer made a comment like that then geeks would be cutting him or her up for that. I might be wrong since I am not a coder but wouldn't keeping software perfection a priority lead to less bugs in the future?
Re:That just doesn't sound right (Score:3, Insightful)
What he means is that they should stop worrying about philosophical arguments and just write a good browser that does things well. I mean, writing 'perfect' code is nice and all, but apparantly, it doesn't really matter. Compare Konqueror's rendering with Safari's - Safari has recently been coded to pass the Acid2 test. How is Konqueror doing in that respect?
So what
Some times a little conflict is good.. (Score:4, Insightful)
Also, if anyone has the "capital" to expend on criticizing KDE, it would and should be the people who have made one of the most successful browsers out there to put a dent in IE usage. See, people kind of listen to you when you are successful as opposed to when you sit and whine because your take on things just doesn't seem to be taking off (Debian/Konqueror I'm looking at you).
He has a point (Score:5, Insightful)
Here's a little theory of mine: users are more concerned with having a great UI and having apps that work together than raw speed. Open source desktops used to have the speed advantage, but not anymore. Can anyone honestly say that GNOME is faster than Windows XP's desktop these days? Same for KDE and MacOS X.
For all of this bitching about Apple exploiting OSS, I don't see any recognition that the mere fact that OSX's underpinnings are OSS gives OSS a vote of confidence in the corporate world. For one of the two largest platforms in the world to switch to that foundation is a big endoresement and help lend legitimacy to OSS. The funniest part of this is that KDE's developers are finally discovering the fact that forks do happen. Imagine that, Apple actually forked KHTML for their own needs. Why is it OK for X.Org to fork and go off in one direction, but not OK for Apple to do the same thing? They give the patches back and excuse me if I am at a loss as to how a forked code base is going to maintain a lot of similarity with the original when both are going off in separate directions.
Re:He has a point (Score:4, Insightful)
Then the bad side is that sloppy coding is not only inferior performance-wise, it also leads to maintenance difficulties, as well as security issues. The most notable example being all of the legacy garbage that windows still carries around.
It sounds like the KHTML people are trying to buck the trend, and make a large, but solid piece of software. They're saying that it's not impossible, just that it takes a while. The "computer industry" has been moving at this incredible speed for a while, so fast in fact that it wasn't realizing a lot of the mistakes it was making. There are plenty of examples of how this is making life tougher now. The KHTML guys aren't interested in doing that anymore, they want to do something right, so they're doing it.
Maybe they're thinking of their renderer as more a piece of infrastructure or technology more than an end product for your everyday user. Try to draw a vague parallel to some guy writing code for the space shuttle. There's more at stake when you're sending humans up in a rocket, but the mentality can be the same. We want to get this right, on the first try. It's inherently complicated enough , no need to make things any denser with hastily added features and sloppy coding.
Re:He has a point (Score:5, Insightful)
Everybody likes to talk about how Apple owns such a small share of the market, but in doing so y'all lose sign of the fact that Apple is the fourth-largest computer manufacturer in the entire world, and the second-largest developer of operating-system software. Considering how narrow our focus is, I'd say those are two pretty remarkable facts, wouldn't you?
MoFo getting more like MS by the day, it seems (Score:5, Insightful)
From TFA:
I would not be so sure of that. I seem to recall that the GPL defines source code as the "preferred form" of the program for making modifications of it. If Apple "comments" its patches by referring to numbers in a proprietary bug database to which only they have access, Apple could be accused of intentionally obfuscating its source code, which is a violation of the "preferred form" clause in the GPL. In any case, it's ethically wrong because the free-software concept is meaningless if the provided source code is not realistically usable without having access to essential information about what it does.
Gee, that sounds eerily familiar. Where have I heard it before, that "give Joe Sixpack what he wants and damn software quality" attitude? Marketing fluff at the expense of solidity and security? Oh right, of course, that's the attitude that brought us the virus propagation engine that is Microsoft Internet Explorer. Is it any wonder that Firefox is now on its way along the same route?
Ridiculous. The use of software is demanding less computer literacy by the year -- compare today to the MS-DOS days of twenty years back. But that is in fact a big part of the problem. People should learn to accept that using a computer requires some basic form of clue. If people are not willing to acquire such clue, they should watch TV instead so that they won't harm anybody with the viruses, spam and DDoS attacks perpetrated through their zombified computers.
From TFA (Score:3, Interesting)
Now, the reason for that is basically that more and more users with no idea of computers are able to use it and use it. So it's not a sign of a Software designer failure but a sign that Software designers are doing "The Right Thing" TM and successfully so.
So the following quote
"Over time, software has come to demand an impossibly high level of computer literacy" is basically wrong. Just compare it to the times when the interface was binary machine code.
The base intetion of the article I agree with though...the Safari Engine is much mure advanced than KHTML, due to more pragmatism in development.
As long as you build software on operating systems who still are stuck in the concepts developed 30 years ago, you have to be pragmatic. Basically implementing anything there is a workaround.
Safari and KHTML (Score:5, Informative)
Submitted by carewolf on Fri, 05/13/2005 - 10:33. [kdedevelopers.org]
-
Safari and KHTML againNotice how there isn?t a vs in the title?
Hyatt and Maciej joined us on IRC yesterday, and we had some really good discussions. I might as well also admit that Maciejs comment was true (but out of context). Please notice that that implies we are discussing solutions and a common future. The idea of a common source tree is pretty much abandoned as we have very different goals and requirements, but we are discussing improved cooperation. With Apple just having released Tiger and us preparing for KDE4 we have a unique opportunity for bringing our source trees closer again.
Since Apple is being a nice guy for the time being, I will let them announce how things will improve once we have a solution, but please, no more ?vs.? stories for the time being, we are working on solving it.
Submitted by carewolf on Sat, 04/30/2005 - 13:22. [kdedevelopers.org]
-
Emphasis added by me...I just wish to weigh in on debacle to clear up some mistakes. First of all I would like to say I agree with Zack. The annoying part is not that Apple don?t cooperate as much as they could. They are actually helpfull in answering questions and _tries_ at least to separate OS X specific features in the code (allthough they fail miserably at it). No, our problem are users who think Apple does more and underestimate the effort it takes for us to implement patches from WebCore. We are doing this for free and for fun, all we really want is appreciation for our effort.
Re:Safari and KHTML (Score:3, Interesting)
We are doing this for free and for fun, all we really want is appreciation for our effort.
So are they doing it for fun, or because they want appreciation for their effort?
Where "free" software fails (Score:5, Insightful)
Pursuing Software Perfection is a GOOD THING... (Score:4, Interesting)
But a big part of that is supplying what the users need. I think all three sides of this discussion could learn a thing or two by listening to the others.
You don't get involved in an open source project to write crappy code. You get involved in order to fix a problem that bugs you, show off your coding skills, or do a little good for the community. One of the benefits of coding for open source is that you really can take the time to get it right.
Businesses often fail to pursue excellence in coding because they believe that by taking shortcuts they save money. That's almost always wrong. One of the reasons that Netscape got beat by IE was (and I know I'll get beaten for saying this) that IE was written in a modular way that allowed it to be used more flexibly than Netscape. The IE code was better planned and executed. The developers who joined the Mozilla project took the original Netscape code and hammered on it for a long time to produce the successful browser that we now have. Even so, it was bloated and in need of a lot of trimming. So the Firefox project fixed those problems and now Netscape is based on the Firefox core rather than the original Mozilla core. (Sharing is a good thing.)
Apparently Apple believes that by taking short cuts they save money because the FOSS community will come in behind their engineers and clean up the code for them the way they did for Netscape. Why shouldn't Apple take advantage of the same mechanism?
What happens too often in corporations and is apparently happening in this part of Apple, is that they have forgotten that they are dealing with people. The FOSS crowd seems to have more than it's fair share of idealists, and they dont' like being taken advantage of. Hopefully Apple has figured this out by now and is working on a plan to mend fences. Otherwise it might be very hard for them to get help from the community in the future. It would be a shame for OS/X to fail because of foolish management mistakes on the Safari side.
Open Source can learn a lot from what Appled did, though, even if we don't like how it turned out. Appled focused on fixing things that were causing problems for their customers. They also focused on becoming standards compliant. A lot of FOSS projects come up short in that area. What gets attention is whatever is cool to code or bugging a particular developer. Not enough of the FOSS projects have any real central focus.
Listen, learn, and move on. The best thing that could come out of this whole mess is a good discussion on how FOSS and regular software companies can work together to mutual benefit. Perhaps we need some kind of template agreement that makes responsibilities clear so that the companies involved don't make bad assumptions like the ones Apple seems to have made.
No user satisfaction without software perfection (Score:3, Informative)
Thanks to this perfection, KDE builds and runs, while Mozilla/Firefox can fall over when you pick wrong compiler flags -- especially on "exotic" platforms like FreeBSD/amd64.
The amount of compiler warnings in Mozilla code is astounding. Quite clearly it was written by result-oriented professional engineers, rather than the process-enjoying hobbyists.
Mr. Sarcasm says... (Score:5, Funny)
But if we hadn't waited on software perfection, we wouldn't all be playing Duke Nukem Forever on top of the GNU Hurd.
Re:Blah... (Score:5, Insightful)
Re:Blah... (Score:5, Insightful)
Quite frankly, I'd rather have them arguing - when OSS developers disagree it often highlights issues that people should really be thinking about.
You might like the Solid Wall Of Unity approach but give me chaos any day.
Comment removed (Score:5, Insightful)
Re:Blah... (Score:5, Insightful)
Re:Blah... (Score:5, Insightful)
Re:Blah... (Score:5, Insightful)
These attributes naturally go away as you add functionality to any code. That is a fact of software development.
Re:Blah... (Score:5, Insightful)
And now _we_ are the pain to work with and aren't encouraging participation??
Re:Blah... (Score:4, Insightful)
Bullshit. The KHTML developers brought this discussion on themselves. Apple rightfully took the code, incorporated it into their products, and not only made the modified version available to users of their products but also publicly for anyone wishing to download it.
It appears that the KHTML developers expect Apple to do all the integration work for them. There is nothing in the LGPL that requires this and my reading of both the LGPL and the GPL indicates that requiring modified code to be made available is the spirit of the license. Integrating it back to the mainline is a courtesy but the license specifically does NOT require this.
Sure, it's customary to help integrate it back into the mainline tree but there have been other instances where this hasn't happened. For example, read up on Lucid Emacs (XEmacs) vs. Emacs debacle. You can draw many parallels from that to this. In that case Stallman was working on releasing a new version of Emacs for years and hadn't done it. Meanwhile, Lucid needed certain features and implemented them. When they offered to integrate the work back to mainline Stallman rejected it because he had his own ideas of how it should be written. In addition (and this does not apply in this case) Stallman required copyright assignment to the FSF which was something Jamie Zawinski in particular did not agree with. After much back and forth Lucid gave up and thus the XEmacs fork was born.
The Lucid Emacs developers suggested that their code simply be incorporated into the next Emacs and that if Stallman wanted to rewrite it again that's fine but what they had was already working and better than what was in the tree. Stallman rejected it because he preferred to wait until their rewrite was complete at which point Lucid could try to integrate with the rewritten code.
It should be obvious that this is a *really* stupid decision. The KHTML developers should suck it up and realize that Apple now has a better rendering engine than they do. They should merge in the changes now (including the ones they don't like) and THEN decide to rewrite things if the code is problematic. In the meantime the KHTML users have a better browser. It will take just as long to write code regardless of whether they merge in the Apple changes or not.
This basically amounts to the KHTML developers having a serious case of Not Invented Here syndrome. After trying and failing to get Apple to do the merging work for them they cried foul and posted publicly about how Apple wasn't helping. I'm truly glad it has mostly backfired because it's up to the KHTML project to decide whether they want the code or not. It's not Apple's responsibility to take orders from the KHTML developers. If KHTML doesn't like it then WebCore can remain a fork of KHTML just like Lucid Emacs is a fork of Emacs.
And don't give me any of the shit floating around here about how the KHTML developers merely wanted to point out that Apple wasn't doing the merging work. There are claims in this thread that the KHTML developers are fine with that but they just aren't fine with it looking as if Apple is contributing to KHTML. Well, news flash, Apple *is* contributing to KHTML and if the KHTML developers don't like the way they contribute and didn't want a big media fuss about it then they should have been smart enough not to write about it publicly. It is for this very reason that I *don't* keep a journal on the web.
Re:Blah... (Score:5, Informative)
The KDE-developers commented about the USERS who whine when Safari-patches don't get merged in to KHTML. They never whined about Apple as such. They even mentioned that Apple is abiding with the license.
How exactly are they "pain to work with"? Apple got a kick-ass HTML-code from them, with NO questions asked, no price being asked and with zero red tape! How exactly does that mean they are "pain to work with"? If anything, this incident shows that COMPANIES are "pain to work with". KDE-developers REALLY wanted to work with Apple, but Apple wasn't interested!
Re:KDE should be grateful. (Score:3, Informative)
First, KDE devs are grateful. Read one of the many linked blog entries about how Safari has done many good things for the project, if you don't believe me.
/. and making a completely backwards post that misrepresents everything they stand for. Sit down and STFU.
However, they are angry at something: people like you. Coming here on
Re:KDE should be grateful. (Score:5, Informative)
KDE-guys did not complain about Apple as such. They even specificly mentioned that Apple is abiding by the license. what they complained about were the USERS who whined when KHTML took time to incorporate improvements made in WebCore!
Do you "get it" now, or do I have to hit you with a clue-by-four?
Re:KDE should be grateful. (Score:3, Informative)
Considering that this thing has been discussed quite a bit recently, I would have guessed that by now everyone who is interested on this would have read the ORIGINAL messages that sparked this whole thing? I mean this message [kdedevelopers.org]
Re:KDE should be grateful. (Score:3, Interesting)
Incidentally, no I hadn't read that. I really don't see how all the linked articles follow from that (completely reasonable post). Must be a hugely escalated flamewar which I had no business getting involved in. I apologize.
Re:KDE should be grateful. (Score:3, Funny)
Re:Right as in legal, right as in wrong (Score:3, Insightful)
Apple forked the KHTML engine under the GPL, this requires them to publish their source. Which they do. It does NOT require them to "submit" code patches on ANY OTHER FORK (including the main trunk) at any time, at all. So, mostly or totally, they don't.
At some point, some OSS and Mac zealot saw that Apple had chosen to fork an OSS project to kick off their COMMERCIAL project, and had
Re:Right as in legal, right as in wrong (Score:3, Insightful)
I think that Apple should clearly not only comply with the law of the GPL, but also the spirit. According to the reports, they are sending huge patches that combine many fixes without any documentation. There is no way that the KHTML people will be able to use these, so the work will ult
Re: Do have to admit though........ (Score:5, Interesting)
There are other things marked as recommended (such as OpenGL and OGG Vorbis), and there are others marked as optional (such as LAME).
The problem isn't KDE is bloated, its the way the distros package it (huge monolithic packages that contain a load of different programs), though some distros like Gentoo now provide 1 package per app (which allows you to trim most packages off.
Also comparing KDE to XFCE makes no sense, XFCE is an extremely minimalistic desktop environment (its just a bit more than only a Window Manager). Only comparing KDE to GNOME would make any sense since both are complete desktop environments.