Their plans always seem like: Beta-final release > take long time to finalize it > kill stage
Google Kills Cloud Print
401–410 of 567 posts
Re: Google Kills Cloud Print
#402Re: Google Kills Cloud Print
#403I am quick to complain when Google kills a useful project - but I am not mad about this. It was originally created because Chromebooks couldn't print. Chromebooks have been able to print natively for a while now so that is no longer needed. They are also giving over a year of warning. That's plenty of time for people to migrate to a new service or figure out how to implement an alternative. Again I know the Google Gr…
> They are also giving over a year of warning. That's plenty of time for people to migrate to a new service or figure out how to implement an alternative. Python 2 would like a word with you.
Re: Google Kills Cloud Print
#404I do believe that right after the event of the first google pixel, all google products were “failure” by their standards. they haven’t created anything big ever since. Same goes to Microsoft and their latest product kills. At least their new products are getting better now. Google never created anything significant. That’s why I wouldn’t trust their new products. They really need to stop publishing products that feel…
Re: Google Kills Cloud Print
#405Earlier quoted context omitted.
I have, for many years, told people who get excited about an opportunity they see "don't build your stuff on top of someone else's free." I am starting to think that I need a similar saying about Google.
External dependencies are always a problem, free or paid.
When Google kills off a service, it's usually pretty much impossible to solve.
Re: Google Kills Cloud Print
#406Earlier quoted context omitted.
> Silo it off and just leave it be. Not really possible. It's an internet service that talks to large number of different printers from different manufacturers. Besides the code management issues others have mentioned, services like this require a great deal of product and partner coordination and testing effort to ensure that even small security patches don't break the heterogeneous ecosystem of devices. More import…
What are you going to use after this? A internet available print server? VPN?
Re: Google Kills Cloud Print
#407Re: Google Kills Cloud Print
#408Nothing about Google killing products is quiet anymore. People have noticed, and I wonder if Google is really aware of the extent of the brand damage that headlines like this cause. Printing is the most corporate thing I can imagine, and even though it is not directly related, as a G Suite customer, this would make me extremely nervous.
The damage is real. It was one of the arguments against Google Cloud in my company.
Re: Google Kills Cloud Print
#409Earlier quoted context omitted.
It seems pretty bold and visionary to me. They've lucked out with gmail, chrome, golang, android, maps, etc. and they still have the best search in the world. Having a HIPPO tell everyone what to do, how to do it and when is not visionary. Letting engineers do what they want and then making money from the ideas is.
Chrome was split off from WebKit, Android was acquired. They didn’t build either from scratch. Compare their success to failure ratio to Apple, Amazon and Microsoft.
Re: Google Kills Cloud Print
#410I'm glad to see this one go. When you want to print from one device in a room to another, sharing a copy of the data with Google's servers halfway across the country seems like an odd and privacy-concerning way to accomplish that. I support relatives using Chromebooks and the old fashioned model is printing is much easier to explain and deal with! The wifi printers in my life never seem to maintain reliable connectio…
I bought a cloud enabled printer for my Dad, who uses a Chromebook. The only way I could get it to print reliably was to connect it to my Windows machine via a cable and have my dad email me whatever he wants to print. In other words, I now have two printers in my office to do what I was doing already with one.