61–70 of 567 posts
” We recommend that over the next year, you identify an alternative solution and execute a migration strategy.” Another Google product killed, another migration strategy to execute. What's next?
The fix seems to be obvious, create a separate path, a maintenance and growth hacker path, where people can take ownership of products and grow them over time. Perhaps people could be judged by their market traction, making them sort-of internal entrepreneurs who over a decade or more, get to share the benefits of shepherding their project.
” We recommend that over the next year, you identify an alternative solution and execute a migration strategy.” Another Google product killed, another migration strategy to execute. What's next?
Something enterprise customers love hearing. Ooof imagine being assigned to sunsetting the service and explaining to what enterprise customers it still has.
” We recommend that over the next year, you identify an alternative solution and execute a migration strategy.” Another Google product killed, another migration strategy to execute. What's next?
Quit Google and start paying for services that you value.
That's a bummer; it was a god send for accessing printers without drivers on the client.
Each printer having its own driver is sort of like ... each terminal having its own escape sequences. When printers and terminals were purpose-built electronics with limited hardware functionality, it made sense to put the smarts into the computer and have it figure out which operations were supported by the device. Nowadays everyone just uses TERM=xterm and there aren't physical terminals anymore (even the companies that used to build them will now sell you cheap general-purpose computers that run a full-screen terminal emulator). Printers have gone the same way; there's enough computational power inside the printer itself that you can just send it something like a PDF and tell it to figure things out.
I wonder what this means for the Google Chrome hardware ecosystem...
https://support.google.com/chrome/a/answer/9633006 Chrome OS now has basically full-featured support for CUPS like a normal Linux machine, so you no longer need Cloud Print to print to local printers, and they're adding features to let you use a remote CUPS server.
Said no-one ever.