Live data from Hacker News

Moments in Chromecast's history

blog.google

261–270 of 609 posts

Re: Moments in Chromecast's history

#261

This is not the same thing. My Chromecast dedicated device would put a default nice picture, then wait for a cast. Google TV and this new device displays advertisements, store, and more. I hate it. It's the last google thing in my house. When it dies, google will be gone from my house.

Aww man, this sucks. I had mine connected to a google photos album. I loved that feature.

Re: Moments in Chromecast's history

#262
Any idea whether it has access to the play store or apks can be sideloaded? The heavy AI integration makes me nervous it won't be the case.

It annoying no longer is behind the TV, just copying Apple (an irritating but effective marketing ploy).

Re: Moments in Chromecast's history

#263

They only reason I went with a Chromecast over a Nividia shield was the price. Now that the gap has narrowed the shield looks much more enticing. The pro version can run a PLEX server and has 2 USB 3.0 ports for storage. And Gforce Now is actually quite nice for games where a milliseconds don't matter all that much.

As someone who ran their plex server on the shield for a year, don't plan on keeping it there if you want get serious with it and/or want to open up it up to external users. As your library grows, it will start to struggle and I had to rebuild my library two or three times.

A $100 SFF or micro computer off ebay with an 8th+ gen intel cpu will serve as a much better plex server, with plenty of room for other things like HomeAssistant etc. The iGPU will do 15-20+ simultaneous 1080p transcodes, and my machine idles at around 10w. The shield can serve up 1 or 2.

The shield pro is hard to beat as a plex client, though.

Re: Moments in Chromecast's history

#264

I'm suddenly reminded to ask this community whom I assume might know: Are there any good "dumb tv" solutions out there? I'm thinking 1-4 HDMI ports, and a maximum of RF tuning and input-switching on the firmware. Products would be preferred suggestions, but I'm even at the point of considering DIY solutions, if something looks lego-ish enough!

Any normal TV, just don't connect it to the internet. Use an external box like an Nvidia Shield or Apple TV, its remote will control on/off/volume on the TV via HDMI-CEC. Now your cheap replaceable external box is the internet-connected computer and your expensive wall-mounted TV is an appliance.

Make sure you get one that won't nag you, a friend's Hisense will regularly overlay an annoying splash screen if it can't reach the internet.

Re: Moments in Chromecast's history

#265

They also announced Google Streamer, which is just Google Chromecast but more expensive I guess, and also with the Nest technology for smart home stuff, which they also killed iirc. I have to say, I don't really see this product strategy as being good, or working. Google's product is just a mess, they are nearing Microsoft levels of incoherence. When you compare Google with Apple, it's such a night and day experience…

I agree with your second paragraph for a lot of reasons and product lines of theirs. But -- I decided a while ago to bite the bullet and go whole hog on using Google everything for my personal life (for better or worse). The decision was either to avoid them entirely or resign and buy into the ecosystem. I have a Pixel, my home uses Nest, I use their cloud storage personally, their AI, etc. FWIW it is a better experi…

> The decision was either to avoid them entirely or resign and buy into the ecosystem.

An easy choice that you somehow managed to get wrong?

Re: Moments in Chromecast's history

#266

Chromecast used to be a great product. I had my gen 1 Chromecast for the last 10 years until recently when it got fried by this piece of crap TV I plugged it into. It was exactly what I want in a device: Do one thing and do it well. I decided to replace it with a new "Chromecast" device to find out that it bears next to no resemblance to the original. Today's Chromecasts are just wannabe Roku devices with actual cast…

Can't have nice things indeed. An alt: Apple AirPlay works super well even with Android tvs nowadays.

Isn't AirPlay only good for screen casting as opposed to casting videos directly? My conclusion was that it's not feasible to use AirPlay to cast a video at the full frame rate and sound synced.

Re: Moments in Chromecast's history

#267

Chromecast used to be a great product. I had my gen 1 Chromecast for the last 10 years until recently when it got fried by this piece of crap TV I plugged it into. It was exactly what I want in a device: Do one thing and do it well. I decided to replace it with a new "Chromecast" device to find out that it bears next to no resemblance to the original. Today's Chromecasts are just wannabe Roku devices with actual cast…

Still use my gen 1, the best 20$ spend in my life. I just have a annoying bug with youtube video that google won't fix.

Re: Moments in Chromecast's history

#268
post #23

How much of this is an "end" to Chromecast and a rebranding of Chromecast to "Google TV Streamer"? It seems like the bare-bones experience of a Chromecast being tied to a phone (or browser) is getting replaced with an Apple TV like experience. If this is the case, it might be a (rare) example of a good branding shift from Google. I have had two Chromecasts (the original and an Ultra) and I feel like both were hampere…

the phone/browser lock-in is largely due to lack of a standardized and open protocol to stream content in this manner. in the wireless-display-sharing ecosystem the chromecast is unique in that, when possible, it streams content from the original provider on a local client rather than relying on mirroring your device's display. this gives a better user experience but required participation from each service provider.…

The standardized protocol already exists and it’s called DLNA which Chromecast initially cannibalized in its first release and then basically killed off every single other DLNA provider and app because they Sherlocked the feature into the Android operating system and to the Chrome browser.

Now that they are at risk of being split up for their monopoly, and as they lose an Antitrust case for their search monopoly, they are probably looking to kill off the Chrome brand because Chrome is how they entirely dominated the web, warping it to their standards and killing more open standards in favor of their Proprietary technology.

Re: Moments in Chromecast's history

#269

Earlier quoted context omitted.

> amazon hasn't tried to create a standardized protocol Amazon is pushing Matter Cast, which is in many ways superior to Google Cast, most of all by being open. Its biggest downside is that it's not supported by anyone else.

> most of all by being open Didn't Chromecasts work with DIAL which was an open protocol? https://www.dial-multiscreen.org/dial/protocol-specification

Google Cast was originally built on top of DIAL, but DIAL itself is mostly about device discovery IIRC. Nowadays it's all mDNS instead.

Re: Moments in Chromecast's history

#270

Chromecast used to be a great product. I had my gen 1 Chromecast for the last 10 years until recently when it got fried by this piece of crap TV I plugged it into. It was exactly what I want in a device: Do one thing and do it well. I decided to replace it with a new "Chromecast" device to find out that it bears next to no resemblance to the original. Today's Chromecasts are just wannabe Roku devices with actual cast…

My experience was the opposite: my gen1 Chromecast's unreliable streaming is what made me get a Raspberry pi 3 :) IIRC the problem likely was the lack of support for 5Ghz WiFi combined with crowded channels in my area.
Post reply on HN