Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Kills Cloud Print

support.google.com

Post reply on HN
Print view View original

481–490 of 567 posts

Re: Google Kills Cloud Print

#481

Post by crankylinuxuser »

thefounder wrote: post #27
jfkw wrote: post #10

Of all the free services to kill, this one really hurts. I just got my parents migrated to using Cloud Print with their Chromebooks and iStuff. As I am providing the usual family-plan IT advice from several timezones away, Cloud Print solved the biggest headache of getting their current project printed to their house or office from wherever they are (or me, if I am helping them). Supporting local printers was a time…

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.

Re: Google Kills Cloud Print

#482

Post by fudged71 »

davidwparker wrote: post #102

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.

Consider that Cloud Print certified printers are on store shelves and will likely be sold for the next 6+ months.

Re: Google Kills Cloud Print

#483

Post by macintux »

corporateslave5 wrote: post #458
freeopinion wrote: post #441

Earlier quoted context omitted.

I know it's beside the point, but you stepped on one of my peeves. Google doesn't have to pay their engineers "a lot". They don't have to keep sucking more and more wealthy people into a concentrated corner of California. They could open a modest office in Nebraska and pay some 5-figure salaries. They could hire some run-of-the-mill college grads to work on a "dead" project. They could cut their teeth on low-profile…

Recently Google has actually been low balling a lot of candidates and is nowhere near top of market. In many cases they are refusing to match competing offers, and are even offering people less money than what they are currently making

Heck, they just reached out to me, which means they’re scraping the bottom of the barrel.

Re: Google Kills Cloud Print

#484

Post by birdyrooster »

drewda wrote: post #325
birdyrooster wrote: post #279

Earlier quoted context omitted.

I almost think they let their engineers launch products just so they can’t quit and go to another company.

You just described the official purpose of https://area120.google.com/

Is that Google officially accepting that 20% time is actually 120% time?

I’m proud of them for baring the truth even if it is a bit oblique.

Re: Google Kills Cloud Print

#485

Post by 9nGQluzmnq3M »

dehrmann wrote: post #238
CobrastanJorji wrote: post #159

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…

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

Re: Google Kills Cloud Print

#486

Post by julianozen »

kllrnohj wrote: post #285
julianozen wrote: post #244

Earlier quoted context omitted.

So this works in theory until there is a really bad bug in some part of the code base and there is no one who knows how to fix it. Or it breaks some kind of migration plan. Or it is embedded somewhere on some architecture that slows down an important projects development. or makes an application incompatible with a future OS If they’re not going to keep a team dedicated to keeping it alive, then you get into a situat…

> So this works in theory until there is a really bad bug in some part of the code base and there is no one who knows how to fix it. 10 years of production usage tends to have hammered out all the "really bad bugs." Sure it's possible that something goes wrong, but it's also extremely unlikely that it does unless something in it changes. Which, if you freeze it & silo it off, doesn't really happen. A huge amount of s…

I don't know. I'd bet anything that has been production for 10 years with no feature added means anybody who knows anything about it left ages ago.

Its a cloud service that was started pre-Google Cloud. There is no way that it can sit in perpetuity and not be worried about old versions of Java, old OS, HTTPS bugs, large deprecation plans

Re: Google Kills Cloud Print

#487

Post by cmurf »

I wonder if they'll replace it with IPP Everywhere support? Totally dropping the ability to print out of the box would be disappointing, but I suppose someone could package up an app that enables IPP Everywhere printing. Google Cloud Print might have had more sophisticated discovery.

Re: Google Kills Cloud Print

#488

Post by dredmorbius »

asdff wrote: post #412
remus wrote: post #335

Earlier quoted context omitted.

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

There is an infinite supply of cheap intern labor at every college in the U.S. chomping at the bit to mop the floor at google hq.

Champing at the bit.

https://grammarist.com/usage/champing-chomping-at-the-bit/

Re: Google Kills Cloud Print

#490

Post by bernierocks »

dredmorbius wrote: post #488
asdff wrote: post #412

Earlier quoted context omitted.

There is an infinite supply of cheap intern labor at every college in the U.S. chomping at the bit to mop the floor at google hq.

Champing at the bit. https://grammarist.com/usage/champing-chomping-at-the-bit/

Did you read your own link? Chomping at the bit has the same meaning.
Post reply on HN