Just because Russia's done 75% of the dying doesn't mean they've accomplished a equivalent amount of the progress.

Comparing total german losses (5,533,000) to german losses on the eastern front (4,215,000) shows that the Soviets indeed did the "equivalent amount of the progress.".

Well, the VideoLAN association president Jean-Baptiste Kempf have posted an analysis that indicates that Rémi Denis-Courmonts "defence of his chosen license" might be misguided.

Getting a developer's license has nothing to do with this; Apple is distributing a binary of a ported VLC in contravention of VLC's license. Apple's App Store rules are the heart of the issue: Apple's App Store rules prohibit them from complying with the GNU GPL which disallows adding restrictions to its (now longstanding) terms

According to this discussion, Apple has actually changed their rules in order to allow GPL like licences:

"You agree that the terms of the Licensed Application End User License Agreement will apply to each Apple Product and to each Third-Party Product that you license through the App Store Service, unless the App Store Product is covered by a valid end user license agreement entered into between you and the licensor of the App Store Product (the “Licensor”), in which case the Licensor’s end user license agreement will apply to that App Store Product."

It is the syntax that defines the language, not the runtime environment. If I run ruby in a jvm through jruby, I still run ruby.

From the android developers fundamentals:

Android applications are written in the Java programming language

Hyperbole much?

ZFS concatenates many small random writes into large sequential write operations. This clearly gives better write performance. As for file defragmentation, WAFL features automatic defragmentation. Similar defragmentation is also in the works for ZFS.

In fact, when you modify a file, you write a whole new block, leaving the old block which contained the old data in place. This will not introduce more used blocks (as the old block is freed) and will in fact give a better write performance as the disk head does not jump around seeking blocks to edit.

Whether copy on write can be introduced in NTFS or not is completely beside the point. NTFS does not currently have this feature.

Read up on the features of ZFS and Btrfs. Copy-on-write would be a start.

NFSv4 was released in December 2000, almost 10 years ago. The fact that people still use NFSv3 is that it simply works and it suits most peoples needs. And NFSv3 is not the only protocol that is vulnerable to spoofing.

Yes, because caching app data, inserting exif data in pictures, offering location service API to applications, storing SMS messages and storing browser history are unique to the iOS. As for "the new Safari html 5 database" storing unique IDs in Web SQL databases, this is a W3C specification also currently supported by Opera and Google Chrome. Not to forget that other browsers also stores unique IDs through flash-cookies.
Why do you think that other mobile OSs like Android does not suffer from the same "problems"? Perhaps it is your obvious Apple hate that clouds your reasoning?