And indeed containers ARE a big deal.
Compartmentalization and Virtualization used to be either full fledged emulators (VMWare, and the like) or ultra simplistic mecanism like chroot (which alows some minor way to restrict some file access but weren't really meant for that purpose in the beginning).

LXC had brought actual container (chroot on steroid, isolating not only file-system but everything else).
Now SystemD is helping even further.
At the beginning, LXC more or less meant installing a full distro under a different chroot. With all the problems of installing a full distro (needing to configure it, needing to launch a tons of things while booting it, very slow start of containers). Systemd simplifies this a lot: the system can auto-configure it-self and boot without needed any saved configuration or whatever. Just autogenerating all the needed on the fly. Also faster boot time, because the systemd's umbrella, besides the PID1 deamon (= the replacement of the old school "/sbin/init") also develops tons of other small lightweight clients and daemon the implement the bare strict minimum to be able to start a container without taking into account all the corner case that a full featured alternative might need.

The end result is that we're nearing an era when you could just tick a "run-in-a-jail" check box next to a software that you either don't trust (skype) or a public service that you need to isolate (webserver) and systemd will auto-magically take care of everything needed.

At first I was laughing, but the end of this video just blew my mind !

Now cue-in hordes of facebook users who will inevitably start to complain that facebook changed again their interface, and now it sucks, and that's it, they are going to deleter their account. Definitely. I swear it.
Like at each of the other 5 big changes over the last year.

Apple's iPhone are designed with battery that should not be replaced by the end-user. The only official policy is that you should bring a phone with a dead or dying battery to the shop for replacement, whereupon the salesperson will try to persuade you to buy a new phone because replacing the old battery is almost as expensive as the newest shiny toy.
You can try to replace them, but it's non trivial, you need to actually disassemble the phone, which might void your warranty.

Compare with any other brand sold in Europe:
You just to :
- buy a replacement (either the original part from any phone shop, or by a 3rd party like mugen)
- power off the phone
- open the battery lid (just pushing a button)/swap the batteries/close the lid
- power on
- don't forget to throw the battery in the appropriate recycling bin instead of putting it into trash.
That's it.

(Please note: air-mailing lithium batteries has a special regulation. Some postal service just refuse to handle them "on security ground", even if they are standard conformant, the proper paperwork is filled, and (like everyphone battery, unlike some modelling batteries) the protecting electronics are actually embed inside the battery itself. That's plain stupid. And it might block your possibility to return the battery for RMA)

- For the closed-source windows application that you are running on your open-source wine. (This kind of emulator can bring executing Windows x86 software on your ARM chromebook. Except TFA's emulator is much faster a this than qemu-user-mode).
- For some shitty closed source stuff that you are forced to use (weird proprietary SSL VPN, Microsoft Skype, Adobe Flash, etc.)

qemu-user-mode + wine has been done for some time already. It more or less works for Windows x86 executables on ARM Linux.
(In fact, the first user-mode emulators where designed to help run x86 code back when Apple used PPC).

The novelty of TFA's emulator is its claimed performance.
That's the interesting stuff. Doing translation (like some emulators running on x86 host do) is going to take a lot less CPU than emulating a complete CPU in software (as qemu currently does on ARM host). Which means longer battery life, which is a big advantage in some markets (tablets and smartphone).

This is hard to make working for several reasons.

First, as mentioned by others, not all OSes allow popup windows. WebOS for example, instead pops-up alerts in the lower status bar. The user is the only one who can switch around windows (cards, in webOS). The only exception is, when one application spawn another one, there is a distinct animation making a new card appear.

The second reason, is variability. Your example would require a single task system. In real life, even phone OSes are moving toward even more multi-tasking. The 23752 bytes you mention will be lost in a sea of other memory change. Maybe the malicious application, between probes, would register an increase of memory consumption of about 67849 bytes, because not only paypal's page was opened, but also between the memory check the user received an message and the messaging application started automatically downloading the attached picture. (And that's just taking into acount application with direct memory management. Now, if you add in the mix languages that use deffered garbage collection, memory consumption gets even weirder).

Third reason is also availablity. You example require the paypal page to always have the exact same size down to the byte in order to be easily recognisable. Saddly, in real life, developers are constantly tuning their code. It might be 23752 today, it could be 34756 tomorrow. And that's just the size it-self. You've probably noticed, but nowadays every single company feels compelled to re-invent their interface, Facebook is far from having the monopolly on completely changing its interface whenever somebody sneezes. That means that the bogus paypal page displayed by the attacked software might look like an older version instead of looking like all other current instances. (Now, that's not a guarantee that the user will notice that something is fishy. Less attentive users will probably dismiss it as "Meh, another of these almost-weekly UI re-invention"). Still, these kind of change will make it terribly difficult to use the free memory tracking that you propose.

Last reason: banks. Some banks ask the user to confirm the transaction out-of-band (mine does make confirm credit-card transaction). A user thinking to buy an In-App extra 10$ with paypal would be surprised to receive an SMS asking confirmation for a credit-card transaction of 10'000$.

Other OSes use other windows manager.
Android is the only one using "flinger".
Wayland for exemple is used by the Meago/Tizen/Sailfish OS family.

Same vulnerability won't expose other OSes, but on the other hand, other window manager could also be broken in a different way and be exploited by a different malicious app.

Yup. Either swap between driver, or taking breaks. But indeed, a single driver shouldn't drive more than 2 hours straight any way.
And to come back to the argument I was giving to the parent poster (arth1): if you're taking breaks anyway, why not plugging the car into the charging port, instead of complaining that a charge is slower than a fuel tank (or a battery swap, for that matter).
Unlike a gaz station, you don't need to hold the the charging cable during the whole procedure. Just plug the car, go make a nice break, drink a coffee, and go back to your electric-car once it alerts you on your smartphone that the battery is nearly full again.

Well, of course I don't know the rules of DOT, because I happen to live on the wrong side of the Atlantic pond.

Well, I happen to have a military driving license and I had to fill this stupid paperworks (or at least, the local equivalent).
And yup, here around too, the drivers are required to keep their tiredness in check and take the necessary breaks.

Depends. Here around, planes tends to be expensive if you don't plan your trip well in advance and buy your ticket while still cheap.
If you want to last-minute travel, trains can be cheaper.
If you're part of a small group, doing a road-trip can also be economically intesting.
Also not every destination is easily reachable by train or airplane.
(During autumn, we need to drive around 3hours to reach ski-resort which are already open for pre-season skiing. Car is the only single way to reach them)
I happen to be the only driver in my group, so I'll have to drive the whole trip both ways. And yes I *do* take breaks mid-way and make sure to be rested enough. And yes, my car is also equipped with collision-avoidance systems, just to have extra safety.

Do you realise that you actually *NEED* to to half an hour break after each two hours of driving ? You need to take breaks anyway, in order not to be too much tired and avoiding increasing your risks of accident due to tiredness and loss of concentration.

So, while you're relaxing, drinking a coffee, etc. why not charge the car, instead of just having it sit idle on the parking lot in front of the cafe/restaurant/park/rest-zone ?

Actually, given the prices practised by some ISP, if this number is correct
ads cost you, the end user, *MORE MONEY* (in terms of bandwidth, specially the "video" kind of ads) than earn money back to the ad-supported website.

And then you wonder why I prefer using Adblock/Noscript, etc. and donating a few bucks (bitcoin,etc.) to website I like the most.

Yup, all the while current cars that won't even qualify as "A.I." but simply as auto-brake / collision-avoidance functions already have the ability to slow down, sound an alarm, and in worst situation slam the brakes to avoid colliding with big object (i.e.: avoid killing people without even being able to recognize people or even have the concept of "people" in their code).

We haven't already started bringing automated vehicles out of google labs, and we already have technology to avoid killing people, by using much simpler technology.

These etchics/philosophy discussion indeed look a bit pointless.

A not even that much intelligent car would have notice a long time ago that there two object on the street (no need to identify them. There are just 2 big masses on the road), and the if car is kept on the same trajectory it is set for a collision course.

the would already have started pre-braking, sounding some imminent collision alarm, blinking lights on the dashboard

By the time you reach the situation where a human would need to steer some way or another, a car with anti-collision system would have slowed down and stop at rest (unless the driver has overridden the system by voluntarily smashing down the accelerator against all car's alarms).

No need for complex recognition and identification of pedestrian. Just plain simple recognition that there are 2 masses of significat size.
No need for complex ethics engine evaluation, just being able to notice that said masses currently occupy a place that is intersected by the current trajectory of the car.
No need to aim for one while sparing the other, just slow down and brake well enough in advance (and cars electronics are much faster at noticing and reacting as human's slow reflexes and limited attention (or lack of) ).

I'm not speaking about some potential futuristic technology. I'm speaking about car that are street legal and currently circulating on a road near you. They're not even self driving, but they are already able to efficiently avoid collisions.

We haven't already started producing self-driving car beyond a few prototypes at google's lab, and we already have the necessary technology to avoid both deaths.

All these "ethics in robotic cars" are nice though experiments for a highschool's philosophy classes, but they are completely out of touch with technology. For any of these though experiment, the technology will reach a development level where casualities can be avoided a long time before a car's A.I begin to be able to have an ethics discussion with the philosophy teacher about the value of life.

PrimeCoin and RieCoin currently have no known FPGA nor ASIC implementation and the few GPU implementation don't seem to bring the huge leaps in performance that GPU brought to Bitcoin's SHA256.

It's not that they were designed with the purpose of being CPU-only (ASIC-resistant was never the main foal in creating them).
It's that they are based around actual scientific problems that ARE difficult. Designing silicon for them *would* be a scientific improvement.

...but not necessarily have huge advantage.

You can build an ASIC for pretty much anything, and beyond some point, it might be commercially reasonnable to attempt it (if the market is big enough and there are enough people interested into buying hardware, it might be worth trying to design sellable hardware).

Now the question is: is there an actual gain in doing it? And that's where all the details lie in.
Depending on the complexity of the Proof-of-Work algorithm, it might range from
- PoW is dumb easy. Each jump in technology (CPU, GPU, FPGA, ASIC) result in massive increase in performance. Hashing power jumps forward several orders of magnitude. Each new technology simply obliterates the relevance of the previous generation (that's the case with bitcoins' SHA256 algorithme).
all the way to the opposite:
- PoW is awfully complex. The algorithme has so much requirement, that your ASIC basically ends up being a slightly custom CPU. The only real benefit compared to GPU, is that the ASIC consumes a tiny bit less power when compared to a GPU.

Also, keep in mind that some PoW actually solve real-life scientific problems. If somebody managed to create ASIC hardware for PrimeCoin or RieCoin, there's some publication-worth fame to be made.

Which of the back door are you speaking about?

The one mandated by NSA that they put in hardware of any American owned company ?
Or the backdoors that the Chinese put into any parts that they ship from their plants to US to build computer ?
Or the backdoors that the Russian somehow still managed to cram in even if they weren't in theory involved in the production of that precise piece of hardware ?