It's Webkit based, and that's about where the similarities end (so is Safari and a lot of minor browsers). You could say the same about Chrome for Android too really, there's nothing particularly "Chrome" about it besides the branding. Not sure what sync feature you're referring to, but I think it's probably more of a Google account thing rather than a Chrome browser thing, there were definitely things like that before Chrome was released for Android.

The User Agent doesn't specify it as Chrome anyway, and I believe that they count mobile browsers seperately. Even if it is included, Android browsing only accounts for about 2% of the total (http://en.wikipedia.org/wiki/Usage_share_of_web_browsers#StatCounter_.28July_2008_to_present.29), so it's not really significant enough to sway things.

Sort of. The actual version number of java is still 1.6, 1.7, etc, but it's always referred to (by Oracle officially and by people generally) as Java 6, Java 7, etc. I'm not entirely sure when they did that, but the guy sat at the desk next to me has a "Java 2" book. I guess they got to 1.2 and wanted to make it sound big, but didn't want to change the version number?

Who knows what they'll do when they hit version 2.0.

That's really anything to do with the file system anyway. Recycle Bin isn't a feature of NTFS/FAT, it's a feature of Windows, and there's plenty of things available in Linux that do the same thing for EXT3/4 and I assume work fine for any natively supported FS. It's not like it's magically "undeleting" files, it just moves them to some other location, which the OS may choose to handle differently to normal directories.

Even after you remove it from there, the data's still on the disk, until that part of the disk gets written over. I guess you could have some sort of filesystem level backup of deleted files, but it's still just a lower level abstraction of "moving the file somewhere you can't see it" rather than "removing" it.

In the end, if you're deleting files because you're need the disk space for something else, you're probably going to want to write over those bits at some point. I can't see much benefit of a filesystem level version of 'undelete' besides working across OSs, and that'd actually require the OSs to support it. I guess it'd be a 'catch all' for different desktop environments/UIs/command lines.