Stadia was not good because of physics. Like GeforceNow, it is laggy and artifacty. It’s not a real business because they don’t actually have a significant target audience. It doesn’t matter who runs it. I’ve been saying this for years and predicting this exact scenario but not because of trust. People trust Google enough to be swayed but this product sucked.
Stadia died because no one trusts Google
21–30 of 626 posts
Re: Stadia died because no one trusts Google
#22I have some business stuff hosted on GCP. I'm actually starting to worry about that, I think it would be weird if GCP was discontinued but I don't know anymore?
Doesn’t look good.
Re: Stadia died because no one trusts Google
#23This is kind of an anti chicken/egg situation! What happened first, the chicken got run over so no more eggs, or the egg got smashed so no more chicken? To clarify the analogy: Nobody trusts Google not to cancel a new thing, so they don't invest any money or effort in the new thing, so it gets cancelled.
Re: Stadia died because no one trusts Google
#24Earlier quoted context omitted.
You might want to look into migrating: https://www.theinformation.com/articles/google-brass-set-202...
I got tons of downvote by saying "I would put one service on GCP just out of principle". Wow, I guess I wasn't so crazy.
Re: Stadia died because no one trusts Google
#25Now that search is not working anymore I'm starting to realize how wonderful it really was. You don't know what you have until it is gone.
Still grieving for Google Reader.
Re: Stadia died because no one trusts Google
#26Now that search is not working anymore I'm starting to realize how wonderful it really was. You don't know what you have until it is gone.
>You don't know what you have until it is gone. Still grieving for Google Reader.
Re: Stadia died because no one trusts Google
#27Imagine if you had a Netflix subscription, and still had to pay for every movie you watched. This is what Stadia felt like to me.
Re: Stadia died because no one trusts Google
#28So, I think Stadia died for reasons other than trust of Google.
Re: Stadia died because no one trusts Google
#29This is kind of an anti chicken/egg situation! What happened first, the chicken got run over so no more eggs, or the egg got smashed so no more chicken? To clarify the analogy: Nobody trusts Google not to cancel a new thing, so they don't invest any money or effort in the new thing, so it gets cancelled.
However, if you look at their history, they cancel many many products.
Looking at wikipedia, I see 200 discontinued products (or scheduled like stadia)
https://en.wikipedia.org/wiki/List_of_Google_products#Schedu...
Re: Stadia died because no one trusts Google
#30The thing that I find odd about Google is that it feels like they drink their own coolaid. Reports I've seen suggest that nearly no one knew this was coming. Teams who have been working on ports for months were blind-sided. Employees generally did not know. It just seems like a very poor way to run a business. It feels sloppy and needlessly messy. Especially when providing soft landings is so possible for a company w…
Obviously this isn't the same thing, but yes - this seems right. But, I remember my first time going to Google's campus in 2010 and connecting to their guest wifi network. 1Gbps! Insanely cool! Pulled up gmail and google docs and it worked PERFECTLY! My first thought was "...oh this is why their webapps suck - they have no idea how it's being used in the real world where latency is above 10ms"
Chrome will not run properly on first execution, as in ran for the first time after a cold start of the computer, when executed off a HDD. Why? Because the HDD takes too long to read off data. Chrome expects SSD latency and fuck your computer if it's not residing on one.
When executed off a HDD, I've found Chrome only runs properly from second execution onwards after the underlying operating system has cached most of the stuff Chrome wants in RAM in anticipation of subsequent executions.
I want to say this is optimization for ever more powerful hardware, but I'm inclined to say it's also sheer incompetency that Chrome literally can't fallback gracefully if it doesn't get data as quickly as it wants.