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

461–470 of 567 posts

Re: Google Kills Cloud Print

#461

Post by twothamendment »

ripdog wrote: post #75

>It's enterprise-ready Hahahahahaha oh man they actually wrote that. Sorry for the useless comment, but I just wonder how many companies got conned into basing their printing infrastructure on yet another Google experiment. I don't think it really matters, of course. Android phones have a full set of manufacturer-specific printing drivers which work fine over the local network, and geofft noted upthread that ChromeOS…

"I just wonder how many companies got conned into basing their printing infrastructure on yet another Google experiment."

I use it at home and like it, but when it came up as a potential solution for a project at work this the exact reason we didn't go with it.

Re: Google Kills Cloud Print

#462

Post by manigandham »

sujNansnam wrote: post #415
cwyers wrote: post #360

Earlier quoted context omitted.

> As such, some SRE/SWE team _must_ be responsible for projects that are in the "don't touch"/maintenance phase. 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. That's Google's problem, and it's a problem they might want to look into solving if they want to turn around their reputation for killing products.

Google pays their engineers a lot and they’d need to recruit a lot more of them if they were going to keep running everything they ever killed. That, or stop launching so many new products.

The company is so massive now that it actually has an overabundance of engineers.

Small projects for maintenance don't need entire teams either and can be completely handled by 1 or 2 junior members.

Re: Google Kills Cloud Print

#463

Post by PascLeRasc »

JAlexoid wrote: post #414
kllrnohj wrote: post #220

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…

It's not free to run and it is not generating revenues. Have printer manufacturers pay for it's maintenance, then it's a reasonable argument for jut keeping it up.

You mean, have printer manufacturers pay to maintain software that allows users to continue using their old printers? I don't see that happening.

Re: Google Kills Cloud Print

#464

Post by username90 »

scarface74 wrote: post #439
kevinslashslash wrote: post #409

Earlier quoted context omitted.

And Apple bought NeXT which is what macOS and iOS are based off of. A purity contest of "from scratch" isn't really relevant. Google clearly put, and continues to put, a lot of serious technical work into Chrome and Android which is reflected in their success.

Chrome isn’t a “success” because of any technical work. It’s a success because Google hocked it on their home page. How is Chrome anymore of technical success than other browsers? As far as Android, it came out in the Oracle trial that it only made about $22 billion in profit during its entire existence and the entire ecosystem is still a mess as far as security and updates compared to Windows - ie where one company…

> How is Chrome anymore of technical success than other browsers?

When chrome was new it was extremely innovative with how much space it gave to websites, and also came with orders of magnitude faster javascript. The other browsers then copied Chrome so all of them are now fast and sleek, but back then the difference was huge.

Re: Google Kills Cloud Print

#465

Post by scarface74 »

username90 wrote: post #464
scarface74 wrote: post #439

Earlier quoted context omitted.

Chrome isn’t a “success” because of any technical work. It’s a success because Google hocked it on their home page. How is Chrome anymore of technical success than other browsers? As far as Android, it came out in the Oracle trial that it only made about $22 billion in profit during its entire existence and the entire ecosystem is still a mess as far as security and updates compared to Windows - ie where one company…

> How is Chrome anymore of technical success than other browsers? When chrome was new it was extremely innovative with how much space it gave to websites, and also came with orders of magnitude faster javascript. The other browsers then copied Chrome so all of them are now fast and sleek, but back then the difference was huge.

Orders of magnitude faster than JavaScriptCore in 2008?

Re: Google Kills Cloud Print

#466

Post by LeoPanthera »

filleduchaos wrote: post #429
LeoPanthera wrote: post #413

Earlier quoted context omitted.

Not on the 16" MBP, or any Mac which comes delivered with Catalina. You can't downgrade a Mac to a version before whatever it was delivered with.

I said install both , not downgrade . Admittedly I presumed (perhaps wrongly) that most people here know what dual booting is.

You still can't. You cannot boot a version of macOS earlier than the supplied one, for any particular machine.

Re: Google Kills Cloud Print

#467

Post by kristianc »

rc-1140 wrote: post #437
kllrnohj wrote: post #220

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…

A lot of the responses to the parent are things along the lines of "well it needs to be owned by a team" and all the usual valid cost-related reasons why [x] can't be maintained, and of course that doing so is boring. Isn't this the kind of project that should be reserved for people in explicit learning states such as (for example) novice hires, new hires, and aspiring mangers who haven't done any management before?…

Over time, if the cost of creating a new thing for a company is maintaining it forever, a lot less new things will get made.

Re: Google Kills Cloud Print

#468

Post by username90 »

scarface74 wrote: post #465
username90 wrote: post #464

Earlier quoted context omitted.

> How is Chrome anymore of technical success than other browsers? When chrome was new it was extremely innovative with how much space it gave to websites, and also came with orders of magnitude faster javascript. The other browsers then copied Chrome so all of them are now fast and sleek, but back then the difference was huge.

Orders of magnitude faster than JavaScriptCore in 2008?

Yes, it depends on what benchmarks you ran though. Example:

https://www.zdnet.com/article/google-chrome-is-insanely-fast...

Re: Google Kills Cloud Print

#469

Post by outworlder »

Google, what the heck?

Cloud Print was THE main reason why I never fully switched away from Chrome. It was more reliable than even the "native" printing capabilities of my printer, which would randomly refuse to print, but over Cloud Print it worked every time.

It was also very convenient to send print jobs even while not at home.

Well, thanks for allowing me to get rid of Chrome entirely, I guess.

Re: Google Kills Cloud Print

#470

Post by outworlder »

dcchambers wrote: post #169

I am quick to complain when Google kills a useful project - but I am not mad about this. It was originally created because Chromebooks couldn't print. Chromebooks have been able to print natively for a while now so that is no longer needed. They are also giving over a year of warning. That's plenty of time for people to migrate to a new service or figure out how to implement an alternative. Again I know the Google Gr…

What are the better solutions? I am still trying to find any.
Post reply on HN