Apple Switches (Mostly) To OpenStreetMap
beelsebob writes "In the recent release of iPhoto for iOS it appears that Apple has started using OpenStreetMap's data. Unfortunately, there are still some problems. Apple is currently not applying the necessary attribution to OSM; they are using an old (from April 2010) dump of the data; and they are not using the data in the U.S. Fingers crossed that Apple works through these issues quickly! Apple is now one of a growing list (including geocaching, and foursquare) to Switch2OSM."
Wait really? Germany? Poor maps on OSM? The german mappers go into insane level of detail –take a look at Berlin for example.
I'm unsure what that URL is meant to show because all it shows to me is that they include open-source software as part of OS X. We know that. It's what this article is about.
Your comment was related to whether Apple contribute code back. That page has no information about Apple returning code at all. Stop spreading misinformation.
Now, the facts.
Apple contribute code back. A fair bit of code has been accepted into FreeBSD from Apple. Do they contribute back as much as they should, ethically? That's debatable, personally I'd say no. Recently they're reducing their open-source efforts too (CUPS).
Why can't people just discuss things normally rather than having all this pro-Apple / anti-Apple garbage?
Every time I see a map rendered with different colors and a different style as Google Maps I immediately feel how much I prefer the Google Maps style. Is it only me or is the rendering really that refined that it's just so much easier to spot things and therefore feels better?
WebKit, LLVM/clang, and yes, they even did a lot for CUPS, and zillions of bugfixes across many products. And if you're an OS wonk, you can even look at the entire MacOS X kernel source code and borrow if you'd like, as well as many of the low-level processes that make MacOS interesting. It's true that many of these were not taken up by other products, but that's hardly Apple's fault.
E pluribus unum
The past story with khtml webkit
You mean the one where the KHTML devs complained that Apple was doing big changeset dumps making them hard to merge, so Apple switched to using a public svn repository? Or the one where committed sandboxing to WebKit in a way that (unlike Chrome's) is browser-agnostic and so can be used by other WebKit users?
I am TheRaven on Soylent News