Live data from Hacker News

Google Kills Cloud Print

support.google.com

291–300 of 567 posts

Re: Google Kills Cloud Print

#291

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 hoa…

I imagine everyone has heard of cloud print -- it's emblazoned on the marketing materials of a bunch of printers. It was the single way of printing from Android -- a couple of billion devices sold -- for the longest time, though it was pretty lame having to send a print job to Google so it can be printed on the device you're standing beside. Android 9 added Wi-Fi direct printing which is much more rational -- on a sm…

>I imagine everyone has heard of cloud print -- it's emblazoned on the marketing materials of a bunch of printers

I don't think most people even have printers anymore. If they do they probably have an old one they don't use often.

Re: Google Kills Cloud Print

#292
post #242

Earlier quoted context omitted.

Counter-argument: Just let it sit there and keep working? Outside of security patches, if there even are any, there's always the option of "just stop touching it." After all, the whole pitch of elastic compute is you only pay for what you use. It's not like resources are being freed up for other things here. The software industry is always on this treadmill of churn, leading to stable products continuing to have a co…

> Counter-argument: Just let it sit there and keep working? Outside of security patches, if there even are any, there's always the option of "just stop touching it." That's not exactly possible with a monorepo that has no branches and everything has to be maintained 'in step'. Any time a library breaks API, all dependents must pass tests, and/or be fixed so that they do. Any time a runtime API breaks (think things li…

This. Someone has to be in OWNERS and it’s difficult to find people willing to do this because fixing breakage due to API changes isn’t going to be on anyone’s OKRs. And if it’s not on your OKRs, it’s not contributing to your promo.

Re: Google Kills Cloud Print

#293

Earlier quoted context omitted.

They might not be wrong. Engineers who could be maintaining mildly profitable products could be invented new products that have some percentage chance of being much more profitable. If someone did the math and said the expected value of "engineer working on new projects" was bigger than the expected value of of the the profits of an existing project divided by the number of engineers needed to maintain it, then it'd…

What if they just sold their low-margin-yet-profitable businesses instead of killing them? There are several tech PE firms that specialize in that niche. KKR bought Corel (of WordPerfect fame) recently. I'm also confident someone at Google already had this obvious idea. Any ex-googlers know why they chose not to / cannot do this?

I strongly suspect that it would generally be a massive undertaking to decouple products from their internal ecosystem and render them able to be spun off.

Re: Google Kills Cloud Print

#295

The product has been around 10 years, and they're giving over a year notice before killing it. Sure, Google kills off another product... But the comments here are a bit silly.

Counter-argument: Just let it sit there and keep working? Outside of security patches, if there even are any, there's always the option of "just stop touching it." After all, the whole pitch of elastic compute is you only pay for what you use. It's not like resources are being freed up for other things here. The software industry is always on this treadmill of churn, leading to stable products continuing to have a co…

[deleted]

Re: Google Kills Cloud Print

#297

Google has the corporate equivalent of ADHD. Having talked with ex-googlers and current googlers, the problem seems to be deeply baked into their culture. The incentive structures seem to favor the sexy over the boring, making it much more likely that someone will get promoted for launching products versus growing one. The fix seems to be obvious, create a separate path, a maintenance and growth hacker path, where pe…

That's funny because other than Google Street View, I can't think of any "sexy" things Google has done. It's mostly really mundane (if sometimes well executed) products and me-too style copycats of chat products. Oh and of course tons of horrible ad tech stuff. I can't say Google's launched anything exciting in the past decade. If they're shooting for sexy, they're failing miserably.

Loon, Waymo, and Stadia seem pretty sexy, for entirely new product spaces. And within the current products AR maps, digital assistant, and AI auto complete in Gmail are pretty cool but I guess that's highly dependent on what you as an individual would care about.

Re: Google Kills Cloud Print

#299
post #230

Earlier quoted context omitted.

What's the expected value of not having your brand known for routinely canceling products without much notice? It seems like any company would have to be crazy to want to depend on any new Google service for anything important - and that's bad for Google.

> It seems like any company would have to be crazy to want to depend on any new Google service for anything important. Companies depend heavily on AdWords, gSuite, and Cloud and all three continue to grow. The reputation for canceling projects which aren't working may matter to consumers, but I haven't seen anyone in business mention it in their purchasing decisions.

It might be your vantage point. For several companies I personally engage with this has absolutely been a point of discussion for Gsuite vs O365.

Re: Google Kills Cloud Print

#300
post #167

Earlier quoted context omitted.

Driverless printing has been "the future" for over a decade now (I remember hearing much about it back in 2006 or so), and a concept for two decades. Microsoft first filed the patent back in 1999 [0]. The only thing that's changed is the patent is now expired (as near as I can tell), thus opening the door a bit wider for adoption. But, as with many things, "I'll believe it when I see it." [0] https://patents.google.c…

AirPrint on iOS and macOS does this, no? Not sure if anyone has cloned that in a Windows utility, but a lot of printers support it.

Chrome OS supports “native” printing. I think it’s more or less interoperable with AirPrint.

The problem would be mostly solved if Windows added native support and added a giant warning when anyone tries to install a printer driver saying that it’s a terrible idea.

Post reply on HN