Live data from Hacker News

Google Kills Cloud Print

support.google.com

561–567 of 567 posts

Re: Google Kills Cloud Print

#561

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…

[deleted]

Re: Google Kills Cloud Print

#562

Earlier quoted context omitted.

How was it the right decision? Silverlight was cross-platform, then they made a Windows-specific fork which is WinRT XAML/WinUI (most people don't realize this but this stack originated as a repurposing of the Silverlight codebase directly, it wasn't a rewrite), now they are apparently hoping to make it cross platform again (see e.g., https://www.theregister.co.uk/2019/11/20/winui_winrt_windows... ) It seems like the…

WinUI is based on .net core. Silverlight on .net framework. At the time, it was not easy to port WPF to core ( mostly because of System.Drawing), they did it now and it's a new framework.

Silverlight wasn't built on the full .NET Framework CLR, it was built on CoreCLR which was the direct ancestor of today's .NET Core.

From https://docs.microsoft.com/enus/dotnet/standard/glossary :

"Originally, CoreCLR was the runtime of Silverlight and was designed to run on multiple platforms, specifically Windows and OS X. CoreCLR is now part of .NET Core and represents a simplified version of the CLR. It's still a cross-platform runtime, now including support for many Linux distributions. CoreCLR is also a virtual machine with JIT and code execution capabilities."

Re: Google Kills Cloud Print

#563

Earlier quoted context omitted.

A much easier to use tool that works using inotify is incron. It's basically like cron except for inotify events. I have a one-liner that OCRs all of my incoming scans, and it's immensely helpful.

What do you use to do the actual ocr?

A python package called OCRmyPDF. It has same defaults and works very well for my use case.

Re: Google Kills Cloud Print

#564
post #516

Earlier quoted context omitted.

> Should they leave it on Python 2 with zero security updates, or invest lots of time porting to python 3? Leave it, of course. The only meaningful security risk at this point is something like heartbleed. We're talking security issue in 10 year battle hardened protocol. This is a fantastically rare case. Not something you need headcount on a constant basis to deal with.

"250M printers compromised by Google Cloud Print" is an ugly look. It won't matter at that time that Google rescued a beloved product from being Deep-Sixed.

Right. Is nobody remembering the Google Plus API fiasco?

Re: Google Kills Cloud Print

#565
post #550

Earlier quoted context omitted.

Because why would anyone buy what basically is a CUPS implementation if not for the user data?

Sometimes companies that are doing "basically a X implementation" are still worth a lot.

That is very true. I guess I got too jaded about consumer data sharing/exchange between companies. Thanks for your feedback!

Re: Google Kills Cloud Print

#566
post #350

Earlier quoted context omitted.

Chrome? Chromecast? Chromebook?

Chrome was basically a reskinned WebKit browser earlier on and then they forked it. I doubt Chromecast (the device) is more than a break even if that. It costs the same as a Roku stick and the CEO of Roku said their hardware doesn’t make a profit. They make money from advertising. The Chromebook sells are minuscule.

> The Chromebook sells are minuscule.

Chromebook sales were 21% of notebook sales in the US in Q4 2018 and the percentage is growing:

https://chromeunboxed.com/chromebooks-make-big-strides-in-sa...

Post reply on HN