| |||||||||||||
|
| |||||||||||||
Open-source divorce for Apple's Safari? (ZDNet)Open-source divorce for Apple's Safari? (ZDNet)Posted May 12, 2005 15:51 UTC (Thu) by nix (subscriber, #2304)In reply to: Open-source divorce for Apple's Safari? (ZDNet) by marduk Parent article: Open-source divorce for Apple's Safari? (ZDNet)
The FSF boycott should still stand.This would be very bad for GCC, at least.
(Log in to post comments)
Open-source divorce for Apple's Safari? (ZDNet) Posted May 13, 2005 2:36 UTC (Fri) by njhurst (guest, #6022) [Link] Out of interest, what has apple contributed back? Is there a web page or something listing gcc contributions?
Open-source divorce for Apple's Safari? (ZDNet) Posted May 13, 2005 2:57 UTC (Fri) by marduk (subscriber, #3831) [Link] From what I can see just by grepping the source, they made some contributions to the Objective C/Java backends, the Altivec platform (surprise) and the testsuite.
Open-source divorce for Apple's Safari? (ZDNet) Posted May 13, 2005 7:13 UTC (Fri) by komarek (guest, #7295) [Link] ...and heavens knows what we would do without Apple's objc improvements. Why, just the other day, I said I would switch to MS Visual Objective C if it wasn't for Apple's improvements. And given the widespread adoption of objective C interfaces for popular libraries...
Not that the parent poster said otherwise, but I'll make it clear that I don't think gcc would suffer much had Apple not contributed objc improvements. Probably even altivec improvements don't matter much overall, but at least they're more broadly useful.
Open-source divorce for Apple's Safari? (ZDNet) Posted May 13, 2005 14:30 UTC (Fri) by nix (subscriber, #2304) [Link] Apple employees are *very* visible on the GCC lists, and have been for years. Going by current email addresses in random order the list includes at least Mike Stump, Matt Austern, Dale Johannesen, Mike Stump, Geoff Keating, Jason Molenda, Andrew Pinski, Devang Patel, Stan Shebs (the original One Apple GCC Hacker), Caroline Tice... the list goes on and on, covering C++ standards deities, members of the Steering Committee and experts on just about every part of the compiler (my apologies to the dozens of people I've left off). Many of these have worked elsewhere (e.g. Cygnus/RH) in the past, but they're at Apple now. The influence of these people on the compiler is too large to easily state.
I'd call Apple a fully-paid-up member of the GCC community, active in *far* more areas than Objective C. I'd not say that GCC would collapse without Apple, but a lot of that is because what matters are the *people*, and they'd find somewhere else that let them hack on GCC if Apple stopped giving them time to do that. Apple is certainly contributing a lot of their time to it (and getting a better compiler in return).
I think this proves that the DHTML fiasco is not due to some evil influence intrinsic to Apple. :)
|
|
||||||||||||