Live data from Hacker News

Google Kills Cloud Print

support.google.com

491–500 of 567 posts

Re: Google Kills Cloud Print

#491
post #44

Earlier quoted context omitted.

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.

Contrast with Apple. AirPrint was introduced in 2010 and is still going strong.

Re: Google Kills Cloud Print

#492
post #335
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." 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 is very unsexy, toil-y and you don't get promoted for it - and as such barely anyone wants to do it at Google. I don't think this is google specific. Keeping a dead product on life support is going to get boring for most people after a while.

It’s a feature not a product. Not everything has to be about profit and loss if it’s part of a larger ecosystem. Google Cloud Print was a feature of Android as well as other parts of Google’s ecosystem just like AirPrint is a feature of iOS/MacOS.

But Google has always been piss poor at managing an ecosystem. Just look at the state of Android updates.

Re: Google Kills Cloud Print

#493
post #332

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…

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

More importantly, CUPS and driverless printing standards have solved the problem (os-specific print drivers) that cloud print was designed to work around.

Guess who owns CUPS?

Re: Google Kills Cloud Print

#494
post #332

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

> Not really possible. It's an internet service that talks to large number of different printers from different manufacturers. Of course it's possible. Those printers are not getting updates, either. Nobody is changing the printer side of this. And if they were it'd be a change in the protocol. It's easy to just freeze the protocol (which already happened years ago), and if any printer manufacturer wants something ne…

And how widespread are driverless printing standards?

Very widespread. Most consumers printers support AirPrint for iOS and MacOS.

Re: Google Kills Cloud Print

#495
post #476

Earlier quoted context omitted.

I saw it as a counterpoint to AirPrint. I'd like to know what changed that made Google think they don't really need this anymore. Maybe they think WiFi Direct is going to be the future?

Local wifi-based printing and printer discovery (same as Airprint) is already available on Google devices. No Cloudprint required.

But you still need individual print drivers.

Re: Google Kills Cloud Print

#496

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.

90s and 00s Microsoft was successful in part because they were an incredibly stable platform to develop against. 10 year support goes a long way, and if you paid enough money you could email in your bugs and get custom hot fixes made for issues that annoyed you. Even their /bad/ technologies had long term support. If you built on top of shiny new thing and Microsoft dropped it in the next release, it was still going…

Microsoft didn’t care about developers that was always a talking point. Microsoft maintained backwards compatibility because of a new operating system broke old code, companies wouldn’t upgrade and it made its money from operating systems.

Apple doesn’t care as much about backwards compatibility because it doesn’t really care if you upgrade your operating system - especially on the Mac - or stick with your old one until you buy a new computer. It doesn’t make money on operating system upgrades.

Re: Google Kills Cloud Print

#497

Earlier quoted context omitted.

Expect Chromebooks to get killed as well.

Yeah, especially after that google graveyard website, and all the services axed with no good replacements... You'd have to be a fool to trust any google service for anything.

What, if any, alternatives are there for Google Voice?

Re: Google Kills Cloud Print

#498

Earlier quoted context omitted.

> Engineers...could be invent[ing] new products that have some percentage chance of being much more profitable Doubtful. The successful products to come out of Google are Search, GMail, and GCP. They bought Adwords, Doubleclick, Android, Youtube, and Nest and Fitbit, I suppose. GCP is their only recent win, but it's a me-too late entrant in a market Google should have invented .

You're forgetting Maps, Earth, Docs, Translate, Drive... Also, many of the acquisitions you mention were tiny when bought, and Google has a much better track record of growing and improving them than, say, Yahoo.

Growing and improving yes. Do any of those products help Google’s bottom line or to diversify where their profits come from?

I can see Docs with GSuite especially in education and maybe Drive.

Re: Google Kills Cloud Print

#499

Earlier quoted context omitted.

My 13 year old son can no longer play a large part of our Steam library because many of the games he enjoys are 32-bit only (Geometry Dash, for one) and we've upgraded to MacOS Catalina. My old copy of Adobe Photoshop CS6 also cannot be installed because the installer is 32-bit, although there's reports if you had it installed before upgrading you can force it to run. I can rollback my son's laptop, but I am on the n…

You can install a VM and run an older copy of the OS on your Mac for games.

VMs do not have direct access to the physical GPU. Worse even is that the virtual GPUs on macOS are not accelerated. So for a VM your rendering will fall back on software based (CPU based) rendering. Apple does not expose the APIs which are needed to be able to write a GPU accelerated driver for VMs.

IOW a VM is no good for playing games when using macOS.

Re: Google Kills Cloud Print

#500
post #476

Earlier quoted context omitted.

Local wifi-based printing and printer discovery (same as Airprint) is already available on Google devices. No Cloudprint required.

But you still need individual print drivers.

Not for CUPS compatible printers.

Also HP provides its own apps and integration for local printing from Chrome: https://chrome.google.com/webstore/detail/hp-print-for-chrom...

Post reply on HN