Slashdot Mirror
Safari And KHTML May Never Meet
diegocgteleline.es writes "Announcing that Safari passes the Acid2 test has raised some voices in the KDE world. Apple, they say, isn't playing friendly. They don't provide a CVS history, just the modified files where nobody can understand how and when things have changed. It's quite likely that KHTML developers will have to write their own code to pass the acid2 test. Zack Rusin writes: 'All I'm asking for is that all the clueless people stop talking about the cooperation between Safari/Konqueror developers and how great it is. There's absolutely nothing great about it. In fact "it" doesn't exist.'"
When an open source project says thay cant understand whats happening when they are given the code.
Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
What truth?
There is no dupe
Should Apple hire a nany to walk them through the code that they changed so that the KDE guys are happy ?
From the article:
"All I'm asking for is that all the clueless people stop talking about the cooperation between Safari/Konqueror developers and how great it is. There's absolutely nothing great about it. In fact "it" doesn't exist.'"
Apple is just another Mirosoft, only with a tiny market share. If I had to choose between Apple and Mirosoft, I'd pick Linux any day.
Bitch all you want, but Dave Hyatt's changes to WebCore stand a good chance of finding their way back into KHTML. Both Konq and Safari will then be Acid2 compliant, and arguably more CSS-compliant than Gecko.
Meanwhile, the chances of Mozilla passing the Acid2 test anytime soon are... what exactly?
What we expect is for them to contribute back to the community, in the terms previously agreed, so that the community may benefit from the improvements, the same way as the company previously bennefited from the community work.
Singularity: a belief in the "God" idea with the "demiurge" relation inverted.
Dude. Seriously. Using version control doesn't necessarily mean "check in each feature/bug fix as one change". It could just as easily be weekly check-ins by the one or two guys working on this branch. Who knows. So stop whining, stop acting like you know what the heck you're talking about, and grow up.
so lets get this straight:
apple takes a project, puts a ton of work into it to improve features, usability, etc. and then tells the project developers what exactly they changed, and this still isnt good enough? as you correctly identified, it is a lot of work to pick that apart. the next step that you fail to take is that it was a lot of work to create those changes as well. explaining it to someone else would basically double the workload on the safari team.
perhaps they should be commenting every single line of code with "x was changed here so that foo would work in bar way without interfereing with baz"?
grow up, the grandparent hits the nail on the head - apple had to figure out what the hell KHTML was doing in the first place, and now that theyve got a superior product you expect them to handhold another group of developers to understanding what has been changed and why?
turn up the jukebox and tell me a lie
There's a difference between forking due to differences in opinion and forking because you're being fat, selfish bitches who refuse to contribute fixes in a respectable manner.
Having said that, if it wasn't LGPLed you'd never see any patches at all. Message to the Free Software world: Apple Computer is a whore. It hates you, but loves your candy.
- Chris
But they're not providing any help at all in making their changes useful to the KHTML team. So, there's no "collaboration" at all from Apple's side.
:)
So, let me see if I've got this straight.
The KHTML team wrote a bunch of code. It worked, for the most part, but there were numerous areas in which it could be improved regarding standards support and whatever else.
Apple got the code, improved it, and gave the improved version back.
The KHTML team (or at least this particular member of it) is now whining because they can't understand their own code after someone else has made (presumably minor) improvements to it?
WTF? Are we dealing with C-happy Linux hackers here, or first-year CS students? The tone I'm getting is one of "please have your programmer, who you're paying, go over these changes you made, with us, one by one, and explain what you did and how you did it, since it's suddenly all Greek to us."
Personally, I have no expectation of KHTML somehow magically feature-matching Safari, given that Safari developers are paid to work on it full-time, don't have to worry about cross-platform compatibility, and so on. I don't personally know anybody who expects every feature that appears in Safari to quickly make its way into KHTML, but then again, I try to associate with non-delusional sorts.
Village idiot in some extremely smart villages.
So, in your opinion, which for-profit corporations are doing a better job, and why? I'm genuinely curious who you would select as providing a better example, and what others would think of your selection(s).
Redhat (numerous contributions), Novell/SuSE (Mono, among many others), and IBM (Eclipse, GCC, kernel, Jikes, etc.) have contributed enormously. A true open source contributor doesn't view software as a zero-sum game. When IBM donates code to Linux or Java, they know that they help lots of "competitors" with that as well, but they also know that everybody, including themselves, wins overall.
Apple, on the other hand, still seems to view everything in terms of "us vs. the world" (an attitude shared with Sun and Microsoft). Apple is out to beat everybody and show that their technology is supposedly the best (in reality: not even close).
But I don't really care about Jobs's delusions, all I care about is that Apple keeps lying publicly about their innovation and about their support for open source. The fact is that the company doesn't pay for research and the company does not support open source, and to represent themselves as if they did is evil.