From a security angle, this makes me nervous
I'm willing to try working with the cloud for things like data processing and the like. Further, I'd -love- to stop with the whole "printer driver" bullshit (we've had printers for -how- long and there's no standard interface?).
However, there are some issues at hand here that I think need to be addressed.
A 'cloud aware' printer is one which, presumably, has enough smarts in it to negotiate its place on the network and to transmit and receive instructions from some outside location.
So already it has the base kit required to set up a nice little bug on an internal network.
This already exists today: there are printers, usually the big jobs in corporate offices, that have been (at least theoretically; I've never actually run across one in the wild--yet) compromised into, for instance, echoing the contents of print jobs to some other location. Sniffing packets requires only a little more sophistication.
If you're willing to go so far as to alter the hardware (like that recent story where the 'hack' was detected due to dual power cables [which was about the stupidest implementation of that idea I've seen yet {honestly, it's not like printers are that tough a form factor to cram an extra board into}] which revealed the surreptitious hardware addition of a small computer) then there's a lot more you can do with a printer.
That the printer is controlled by some agency outside your network only serves to further disguise any traces of suspicious traffic.
I'm not going to bother with the comment in the article about 'punching through the firewall'--it's too ambiguous to say if that's intended to echo a security concern or indicate a vpn setup--but I think Google has a lot of work to do to ensure that the proper documents get sent to the proper printers.
I've noticed, while working in IT, that the further the disconnect between the action taken by the user and the result, the harder it is for the bog-standard user to figure out what's going on. Most users can manage a CD tray OK enough; they hit the button, and the tray pops out. Immediate result.
However, there is already a problem with the existing disconnect between the action between hitting the "print" button and receiving a printout. How often, those of you who (like me) work in IT, have you witnessed a user filling up a print queue with dozens of print requests to a printer that, say, requires a toner change?
Introducing a further disconnect (and I predict approximately ten minutes' use before the first "it must have got lost in the cloud" comment shows up from a clueless user) will only serve to make matters worse.