This should help muffle all the cries that Apple gives noting back to the open source community.
In fact, Apple is famous for giving back to the open source community. Not sure where all those cries came from or what they're based on.
This should help muffle all the cries that Apple gives noting back to the open source community.
Aren't all code changes patches? No matter what, if you've been branched for a while and have multiple changes to multiple files, merging is time consuming when the branch and trunk are both changing.
Things are already done in parallel, its called threading. Process swicthing is alot heavier than thread switching, so performance will go down, but stability up, cause processes can't harm each-other directly.Performance will increase since things can b done in parallel.
...I've switched to Chrome but will consider switching back for WebKit2.
In fact, Apple is famous for giving back to the open source community. Not sure where all those cries came from or what they're based on.
What's not to like about Chrome? (I'm currently using Safari + a bit of Firefox but I'm seriously considering a switch to Chrome)...
No, I believe these were patches in the form of diffs - so only the changes between version x and version y, as opposed to the entire code file could be merged more easily.
Back to the more esoteric and technical rumors. I guess the ipad is out and the iphone OS 4 has been demoed. Also the next iphone's features are mostly known. Gonna get kinda dry around these parts I guess.
Getting a bit off-topic, but if a file has versions 1.1, 1.2, 1.3, then there are two diffs. Even if Apple submitted the two diffs, instead of one diff covering the difference between version 1.3 and 1.1, it is straight-forward to generate that diff. It is a pain if the number of diffs per file are different. So, it's a bit more work but scriptable.
With any modern source control system, the real merging work comes when there are conflicts. I suspect this as the source of friction rather than how the patches were submitted.
Anyway, I've heard that build engineers get paid the most in the software industry. It's a rather bland job, but very important.
EDIT: I followed the link in Stella's edited post. It definitely sounds like the problem was "conflicts" in the code base caused by Apple making bug fixes that were incompatible with how/what the open source community wanted. For those who aren't SW engineers, a conflict could be two possible lines like:
"a = CONSTANT;"
"average = CONSTANT;"
Both are correct variable assignments, but one team might prefer the shorter name and the other the longer name. You can't have both and the merging engineer must make a choice.
This should help muffle all the cries that Apple gives noting back to the open source community.
I think "diff" in this context means version number, but rather Apple just gave the open source community a file that said what was different. For example: say you had a file with 1 paragraph of text in it. Apple comes along and adds a second paragraph to the file. Instead of giving back a file that has both paragraphs, Apple gave back a file that says, "Add this paragraph to the end of the original file". That means there are two files and someone has to go in and merge Apple's file back into the original file. WHile it's fairly easy to just add something to the end, if it's a word here, another word there, that's hard to do. Kinda like the difference between Apple's delta updates & combo updates. The person you quoted might mean Apple should give the WHOLE file, original + changes, not just the changes.
I think "diff" in this context means version number, but rather Apple just gave the open source community a file that said what was different. For example: say you had a file with 1 paragraph of text in it. Apple comes along and adds a second paragraph to the file. Instead of giving back a file that has both paragraphs, Apple gave back a file that says, "Add this paragraph to the end of the original file". That means there are two files and someone has to go in and merge Apple's file back into the original file. WHile it's fairly easy to just add something to the end, if it's a word here, another word there, that's hard to do. Kinda like the difference between Apple's delta updates & combo updates. The person you quoted might mean Apple should give the WHOLE file, original + changes, not just the changes.
in one ear said:does this mean security will become as good as chromes ?
Back to the more esoteric and technical rumors. I guess the ipad is out and the iphone OS 4 has been demoed. Also the next iphone's features are mostly known. Gonna get kinda dry around these parts I guess.
What's not to like about Chrome? (I'm currently using Safari + a bit of Firefox but I'm seriously considering a switch to Chrome)...
Who would rate this "negative"? (Well, probably the same eight people who rate every post negative, but why? Do you not like sandboxing?)
Because Apple has not come out yet with it's new MacBook Pros![]()
EDIT: I followed the link in Stella's edited post. It definitely sounds like the problem was "conflicts" in the code base caused by Apple making bug fixes that were incompatible with how/what the open source community wanted. For those who aren't SW engineers, a conflict could be two possible lines like:
"a = CONSTANT;"
"average = CONSTANT;"
Both are correct variable assignments, but one team might prefer the shorter name and the other the longer name. You can't have both and the merging engineer must make a choice.