Here's a list of devices that either have or will get Jelly Bean.

Also, this page shows a (fairly complete, though I hesitate to say "complete" for the fact that there's almost certainly at least one Android phone/tablet not mentioned on it that exists somewhere...) list of Android devices, including what version they run. It contains 41 mentions of 4.1 and 11 mentions of 4.2.

Most people don't know what Qt is, though. They don't realise how much of the software they use uses it.

Or for those already familiar with the Matlab language (or who know they'll need to become familiar with it): Octave.

Since 112 takes place in Europe, we should be remembering the 11th of February. As a South African, I do so with pride (11-2-1990: The day Nelson Mandela was released from prison).

Just in case anyone is wondering: the NANP has area codes and exchanges starting with 2-9, which means that 112 would be globally unique on NANP (in fact, 11 would allow the phone system to register that you must be dialing 112, since the only time you'd start with a 1 is when dialing the NANP country code followed by an area code, or when dialing the emergency services.

The difference here is that Windows has roughly 90% of the desktop marketshare (what is generally considered a monopoly market share), whereas iOS has an estimated 20%-50% (depending on who you ask) (30%-50% for Android).

Source

Anyone who has root access to the device can read and write all files in all folders. That's why they call it the superuser.

No they don't. The iMac and the Mac Mini are desktop computers (or computers in the fashion of desktops), because that's their use case. Typically, when one buys an iMac or a Mac Mini, the competing products they're looking at are the HP, Dell, etc. DESKTOP lines. Likewise, someone buying a Macbook will look at other Laptops.

Perhaps the programmers they have working on the Linux version are better than the programmers they got to do the Mac version? Perhaps they know the system better (e.g. the programmers writing the Mac version are Windows programmers who got reassigned, vs. the Linux version where they specifically hired Linux devs)? Perhaps Valve learned some stuff when porting Steam to Mac that they couldn't apply to the Mac version (because it was too far along), but had the advantage of applying to the Linux version? Perhaps they have another reason to make the Linux version particularly better (rumoured Steam console)?

Point is, there are lot of reasons a Linux port might be better than a Mac port.

Have you checked O'Reilly's stance on their ebooks?

Furthermore:

It took me a decade of living in the US before I could do that. If you're not an American citizen yet, you're not technically African-American. Just African.

It's quite possible that you already had binaries of the non-open source components. You're free to do what you want to the open source components of the SDK (within their open source license), but all other components (which may include components touched by "make sdk") fall under this agreement.

It wouldn't even do that much. It would prohibit forking the non-open source PARTS of the SDK. Since the open source licenses would override this agreement for open source components, it would be perfectly acceptable to fork those portions. Furthermore, one could then re-implement the other portions of the SDK.

IIRC, it's also about how the software is connected. If GPL'd libraries are linked, then the software that links to the library has to be GPL'd (that was the motivation for the LGPL - you don't have to do that). However, if the GPL'd software is a separate executable, it's much less certain (and many would argue that any software can make a process call to GPL'd software without breaking the license). One example of the latter is the Linux kernel. If, by being a "part of a whole", the Linux kernel were to force userland software to be GPL'd, things like TiVo, Android, and binary drivers wouldn't be possible. No MATLAB for Linux, no Firefox for Linux (unless it were relicensed), etc.

They could have simply contributed to KHTML and been done with it. The way they did it really screwed over the KDE project in a manner from which they have yet to fully recover.