Live data from Hacker News

Google Kills Cloud Print

support.google.com

41–50 of 567 posts

Re: Google Kills Cloud Print

#42

I can see why people will miss it, but cloud print is always on my short list of things I remove/disable when setting up a phone. How many average people still own/need a printer often enough to not just go use one at the library/kinkos?

We set it up at our condo building lobby on a nice MFP for anyone to use. Was a great, easy to use solution.

Can your printer be accessed via local wifi network / rendezvous?

And does Chromebook support that?

Re: Google Kills Cloud Print

#43
post #4

Wow, that's a real shame, because Google Cloud Print was one of those nice little services that did ONE THING amazingly. I loved that I could print stuff from anywhere and it would be sitting on my printer when I got home. If I am working at a coffee shop, or out of town and bought something that needed to print a receipt, or a confirmation, or anything else. I could print it through Google Cloud Print and it would b…

I suppose the workaround is to send all your printables to a Google drive folder, and then have an app on your devices that send those printables to the printer whenever the printer is visible on wifi. Not sure if Android offers sufficient APIs for that though.

Re: Google Kills Cloud Print

#44
post #4

Wow, that's a real shame, because Google Cloud Print was one of those nice little services that did ONE THING amazingly. I loved that I could print stuff from anywhere and it would be sitting on my printer when I got home. If I am working at a coffee shop, or out of town and bought something that needed to print a receipt, or a confirmation, or anything else. I could print it through Google Cloud Print and it would b…

Wait did you just say you liked a google service and they killed it? HA! Welcome to the world. Google services always find a great niche. The problem is google wants MAJOR hits or bust.

No, they just achieve runaway success on mass scale.

From Google's perspective the flypaper is just bigger; its contents are no less needle-moving.

Re: Google Kills Cloud Print

#48
post #2

Good news: they give you a year to transition. Bad news: you'll have to buy a new printer if it doesn't play nicely with CUPS. Google really is the land of the walking-dead projects.

A year is plenty of time to learn to code and write yourself a CUPS plugin...

Nobody's gonna pay you to do it tho...

Re: Google Kills Cloud Print

#49

I wish Google could at least release the code of killed projects as opensource.

Generally, Googles infrastructure is so unlike existing opensource systems that even if you had the sourcecode in-hand, the effort required to get it compiling and running while re-implementing all dependencies would be almost as much as starting from scratch.

The opensourcing of Bazel and absl:: is a big start - but there are a lot of core Java libraries you'd be missing, and all the loadbalancing, identity, config and storage systems would all need shims to slightly-incompatible opensource solutions.

Re: Google Kills Cloud Print

#50
post #24

Would be nice if they could open source it, though I suppose it depends on Google internal frameworks and services none of us has.

I think they should opensource it in a non-compiling, non-working state, as a gesture of openness.

I bet someone would go to the effort of patching it up and getting it to run.

Only disadvantage is probably that "cloudprint.google.com" is probably hardcoded into millions of printers worldwide, so even if you could run it on your own server, your printer will never work with it.

Post reply on HN