4 ms·
> So the ancient WPS printer in my garage is entirely unsupported without deploying a computer running Windows or macOS, installing Chrome, and registering a "c
by scottlamb 7y ago
> So the ancient WPS printer in my garage is entirely unsupported without deploying a computer running Windows or macOS, installing Chrome, and registering a "classic printer"
I think the support text is wrong—you could do this on Linux as well. It'll be a moot point though when Cloud Print shuts down.
> Why is CUPS gimped so badly on ChromeOS?
Have you tried recently? I don't think it is anymore. Yesterday my Chromebook seemed to just see my printer on my local LAN (via Rendezvous, I assume).
I agree these product/support docs you linked are pretty alarming. But I think the actual situation is (or if not is, will be) much better for basic ChromeOS in simple situations:
* auto-discovered network-connected printer on the same LAN as the Chromebook
* network-connected printer where you know the hostname and it's reachable from the Chromebook
* USB printer connected directly to the Chromebook
Hopefully those docs will improve soon...
Note that while I work for Google, I don't have any inside knowledge of this.
- branon 7y agoI have not tried recently. The new support articles I've uncovered seem to suggest that the situation has vastly improved. I'm still salty though, and I've put too much work into my Python script to really be concerned about switching to the more "correct" process that was previously denied to me. The sad fact is that once a consumer realizes the device they've bought is encumbered with artificial limitations, they might not trust it even when (if!) these limitations are lifted later.