> The receiver device runs a scaled-down Chrome browser with a receiver application that receives data over Internet Protocol and transmits it to the television via HDMI.
Very cool, though incredibly surprising (a browser is an intensive, complex thing, so will people have to constantly be patching their Chromestick?), especially given that once you add the cost of synchronizing all interactions, it seems so much easier to simply video grab the tab.
If anyone has this device, what is CPU usage on the source like when tab-casting?
If anyone has this device, what is CPU usage on the source like when tab-casting?