31–40 of 84 posts
The problem I have with Google tech, especially after the new Nest stuff has to come to light, is that there's no guarantee they'll support it for very long. It's entirely possible that I'll incorporate this into my workflow, just for Google to kill it off a year later.
Any instructions on how to use this?
The problem I have with Google tech, especially after the new Nest stuff has to come to light, is that there's no guarantee they'll support it for very long. It's entirely possible that I'll incorporate this into my workflow, just for Google to kill it off a year later.
Yeah this is way too niche, ill-defined, and overlapping with existing products to ever survive. Why don't they just make a convenient set of clients or extensions to map into a product that's not going to disappear next quarter, like Drive/Docs/whateverthehellitisnow.
https://chrome.google.com/webstore/detail/save-to-google-dri...
Leads to 404 for me.
The problem I have with Google tech, especially after the new Nest stuff has to come to light, is that there's no guarantee they'll support it for very long. It's entirely possible that I'll incorporate this into my workflow, just for Google to kill it off a year later.
The problem I have with Google tech, especially after the new Nest stuff has to come to light, is that there's no guarantee they'll support it for very long. It's entirely possible that I'll incorporate this into my workflow, just for Google to kill it off a year later.
Should Google only work on things that it could guarantee to run for at least a few years no matter how it is performing?
The problem I have with Google tech, especially after the new Nest stuff has to come to light, is that there's no guarantee they'll support it for very long. It's entirely possible that I'll incorporate this into my workflow, just for Google to kill it off a year later.
For their most popular products...I've found them to be pretty stable...little apps I've created using their Javascript mapping still function even though I knew so little about JS back then. I keep forgetting that I have a Google Voice number, and it still works fine even though it's been years since I've last used it on a regular basis.
Of course I think of Amazon being the most stable of platforms, but those are dev focused, with APIs that they've dogfooded too much to just drop. OTOH, they've cut a few public-facing conveniences, such as Send-to-Kindle integration from third parties (or, that's what I'm assuming, given the roundabout way that is now needed to import O'Reilly ebooks).
The problem I have with Google tech, especially after the new Nest stuff has to come to light, is that there's no guarantee they'll support it for very long. It's entirely possible that I'll incorporate this into my workflow, just for Google to kill it off a year later.
Should Google only work on things that it could guarantee to run for at least a few years no matter how it is performing?