A shared computer should not let users see other users' private files (and browser caches are most definitely not world-readable). This is what happens with Android multi-login, Chrome OS and traditional Linux distros. I'm fairly certain the same is also true for Windows and Mac OS X.
If I temporarily let someone use my computer with my account, I sure as hell keep an eye on what they are doing, because the thing contains stuff about me that's much more sensitive than anything that paypal or my bank will ever know.
"Rooting" means exploiting a security flaw to get root privileges in a device that is designed to prevent users from doing that (e.g. the iPhone or the Android phones sold by some US network operators).
Bootloader unlocking and root access was available and well documented on the first Android device designed by Google (the Nexus One), simply by running the command "fastboot oem unlock".
The same command worked on the second Android phone by Google, the Nexus S, and all subsequent devices, including tablets: Galaxy Nexus, Nexus 4, Nexus 7 and Nexus 10. Unsurprisingly it also works on Glass.
It's just a well know feature of all the devices created by Google. Details: https://plus.google.com/112413860260589530492/posts/jYHhKHYwUJ2.
Google's documentation on how to "root" your Android devices: http://source.android.com/source/building-devices.html.
In Italy, like the rest of the EU, public money must usually be spent through transparent public contracts awarded to the lowest bidder that satisfies all requirements.
To make sure that Linux or LibreOffice don't cause problems the trick is very simple: they put e.g. "Windows 7" or "Microsoft Office 2010" in the requirements and pretend to have open competitive bids by comparing offers from different resellers for Microsoft software.
Another common trick is to let the situation degenerate until it becomes an emergency. At that point the law allows contracts to be awarded directly to a company arbitrarly chosen by a politician. This explains "emergencies" that last decades like the garbages crisis in Naples.
Jazelle has been gone for years. None of the Cortex series include it. It gave worse performance to a modern JIT, but in a lower memory footprint. It's only useful when you want to run Java apps in 4MB of RAM.
Are you sure? ARM advertises it as part of all architectures from ARMv5 to ARMv8: http://www.arm.com/files/downloads/ARMv8_Architecture.pdf.
Getting back on topic: the last ARM architecture, ARMv8, is far from what was called "RISC" back in the '70s. E.g. it can run instructions of different sizes (16 vs 32 bit), it has 4 specialized instructions for AES, registers with different sizes (32, 64 and 128 bits), instructions for running a subset of the Java bytecode, a rich set of SIMD operations and specialized instructions for SHA-1 and SHA-256.
Similarily the architecture supported by the new Atom chips (which is AMD64/x86-64 BTW, IA32 is only present for backward compatibility) is almost universally run on RISC-like processors that have instruction translators. Considering that the increased density of the x86-64 instructions usually allows to save more cache transistors than the ones required for decoding the instructions themselves, I think that the power consumption differences that we see are more due to the implementation and different traditional focus areas of ARM vs Intel/AMD than inherent differences in the instruction sets.
Ian Hickson is the editor of both docs (he's actually the editor of the main HTML standard, the WHATWG one; the draft hosted by the W3C is really nothing more that an old and incomplete copy that nobody among browser vendors takes seriously).
He explained very clearly the past and current situation: http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Jul/0119.html
And, yes, the WHATWG has done an excellent job so far, bringing much needed features to the web and creating an era of faster and more interoperable browsers. If they had just waited for the W3C we would still be stuck with HTML 4.01, IE6, Flash and other plugins.
Also this is not a new development, HTML (from WHATWG) has started gradually leaving the HTML5 (from W3C) behind a long time ago. Where the two differ, all major browsers (including IE) either already follow HTML or plan to. See this post from more than a year ago: http://blog.whatwg.org/html-is-the-new-html5
When people talk about HTML5 features in browsers and websites, they actually refer to the HTML standard. The HTML5 "working draft" on the W3C website doesn't even support the old 2D canvas API, which is implemented by all browsers!
They tried with an atheist but she left the blacklist empty.
But why do get the strong feeling they meant to say 'after PCs now consoles too'? Am I reading too much between the lines here?
Quite the opposite: you're reading too little.
They're interested in game consoles because they already have the capability to hack into PCs, just like every other script kiddie on this planet.