Live data from Hacker News

Google Kills Cloud Print

support.google.com

111–120 of 567 posts

Re: Google Kills Cloud Print

#112
post #61

” We recommend that over the next year, you identify an alternative solution and execute a migration strategy.” Another Google product killed, another migration strategy to execute. What's next?

Quit Google and start paying for services that you value.

What's a paid alternative to Google Cloud Print?

Re: Google Kills Cloud Print

#114

I know Microsoft gets a lot of flak for their historical support of legacy systems, but on the flip-side it means that as an enterprise you trust that they won't abruptly deprecate something you use.

Despite all the disdain for Microsoft in the spirit of slashdot sentiments, Google has turned out to be worse in many respects.

Re: Google Kills Cloud Print

#115
99.5% of the people upvoting this article had neither used nor heard of Cloud Print before seeing this headline.

Look, I too got annoyed when Google killed Reader. It sucked for a couple days. I moved on.

This doesn't even register as a product. It was an experiment that wasn't needed, so they killed it.

Holding onto every silly project you ever worked on doesn't make you responsible, it makes you a directionless hoarder. Even Google doesn't have infinite bandwidth (heh) to work on pointless side-projects.

They aren't killing Gmail. Or GCP. Or Maps. Or anything else you ever used. Let it die. Don't upvote this post just to use it for ammunition on some overly-generic tirade against Google product management. You are just adding noise to the world.

Re: Google Kills Cloud Print

#116
It's very funny that the article itself calls out most people commenting here > Regardless, Google is getting savaged by bloggers for killing yet another service, one that most of them never even tried, let alone used regularly.

Re: Google Kills Cloud Print

#117
post #67
post #57

That's a bummer; it was a god send for accessing printers without drivers on the client.

Printers are standardizing on a thing called "driverless printing," based on having some common Page Description Languages (or having the printer have support for handling a PDF directly): https://wiki.debian.org/CUPSDriverlessPrinting#Driverless_Pr... Each printer having its own driver is sort of like ... each terminal having its own escape sequences. When printers and terminals were purpose-built electronics with l…

You're writing a bit of stuff, may all sound right.. But I'm not sure about what that hasto do with OP's statement? How can I now tell my printer in my home network to print a document from my smartphone on the go or my work PC? And that without installing some half-baked monster app for each printer vendor.

Driver-less printing is great if I'm in the same network, but not so if not.

Re: Google Kills Cloud Print

#119

I know Microsoft gets a lot of flak for their historical support of legacy systems, but on the flip-side it means that as an enterprise you trust that they won't abruptly deprecate something you use.

Flak? You mean, respect from people who were around for a few years (or decades) and saw the sexy new thing change from under them in incompatible ways?

I've seen some reprieve towards MS for their new things not being nice enough, but never for their old thing continuing to work mostly without a hitch.

Post reply on HN