Maybe you want Airplay to be more the focus of Apple TV, but that state of affairs doesn't sound at all like Chromecast.
Chromecast seems to be a method for driving-devices to send pointers to internet video streams or web pages, for the dongle to queue, download and then send to the display. The apps/content don't live on the mobile device at all. They live on remote internet servers. The device is just feeding a queue.
I'd also add a wrinkle to your statement about devices being awesome as typing/searching interfaces: that's true, but they come with negatives.
The real problem with "device as brains", is that your device does many other jobs. And you may not want those jobs in-your-face when you're watching a movie, or showing pictures, or even just trying to add background-music to a dinner party.
Devices are more difficult to deal with when you just want to pause something, the notifications are there, the temptations are there and the social negatives are there [1].
But while everyone's tossing out Airplay wish-lists -- it'd be nice if I could airplay a movie to my TV but have the audio still piped to the headphones.
[1] You may be trying to switch playlists, but to everyone else it looks for all the world like texting.
While its primary mode is indeed method-for-sending-pointers-to-media, it also has an option for streaming the contents of a Chrome tab directly to the Chromecast device [1] ala-VNC. With caveats: that feature is still in beta and requires a fast computer/connection.
It is using open standards upnp+rest api+websockets. The mirroring part is done with opus and vp9. Miracast on the other hand is drm(big players only) over drm(restricted content) over drm(it will only work with closed source software). Miracast will only live in heads of Balmer worshipers and maniacs, who love to to create long power point presentations with lots of bullet points.
The DRM in Miracast is pretty much the same as the stuff sent over HDMI. Wouldn't surprise me if the Chromecast requires HDCP like Apple TV does.
Also, if your assertions are correct, please update the Wikipedia page, which states that "At present time, Miracast Source is mainly active on Android platforms." which seems to conflict with "only ... Balmer worshipers".
According to AvsForum news: "streams it directly to the Chromecast device from the cloud". So you are right about it being somewhat different from airPlay, but it clearly intends to be seamless, and not have a queue / download cycle, but stream it just as it would to your browser.
It also says "including Youtube, Netflix, and Google Play, Vudu, Hulu... anything that plays in a Chrome browser" which sounds a little different from "a method for driving-devices to send pointers to internet video streams". The latter seems to imply programming changes on the provider's part, whereas the former clearly does not. (I don't actually know which is true, just pointing out the differences).
>"streams it directly to the Chromecast device from the cloud". So you are right about it being somewhat different from airPlay
AirPlay will send a URL to the Apple TV if possible. If you're streaming a video from a web page, it most likely will just send the URL to the Apple TV. The only communication with the device is the control channel.
'queue' was referring to chromecast's touted ability for, say, me to be able to send a video to the chromecast and then you to send one for it to play 'next'.
And 'download' was to make explicit the chromecast is downloading the content from the internet itself; it's not taking a videostream from the device as in the Airplay/"device-as-brains" scenario.
I'm not sure there's any difference between the phrasings in your second paragraph. I certainly didn't intend to imply anything different.
Chromecast seems to be a method for driving-devices to send pointers to internet video streams or web pages, for the dongle to queue, download and then send to the display. The apps/content don't live on the mobile device at all. They live on remote internet servers. The device is just feeding a queue.
I'd also add a wrinkle to your statement about devices being awesome as typing/searching interfaces: that's true, but they come with negatives.
The real problem with "device as brains", is that your device does many other jobs. And you may not want those jobs in-your-face when you're watching a movie, or showing pictures, or even just trying to add background-music to a dinner party.
Devices are more difficult to deal with when you just want to pause something, the notifications are there, the temptations are there and the social negatives are there [1].
But while everyone's tossing out Airplay wish-lists -- it'd be nice if I could airplay a movie to my TV but have the audio still piped to the headphones.
[1] You may be trying to switch playlists, but to everyone else it looks for all the world like texting.