5 ms·

Was anyone really using this feature? Even the author sounds like he wasn't actively using the feature. He entered some data 6 years ago, and went back today to

Was anyone really using this feature? Even the author sounds like he wasn't actively using the feature. He entered some data 6 years ago, and went back today to find it was missing.... He didn't even notice until almost a year after it was removed. Keeping every feature around, even the unused ones that look like failures, is a bad idea.

tomohawk 8y ago
Repeatedly destroying trust by dropping things and breaking things for people, is a bad idea.
- gboudrias 8y ago
  At this point Google projects are basically less reliable than hobby projects.
  - psergeant 8y ago
    But hey, come build your company on top of GCP!
    - stefano 8y ago
      Funny thing is, people are lining up to do just that. I think that's a symptom of an industry where following the hype is more important than long term stability.
      - runeks 8y ago
        Or maybe they’ve carefully weighed their options, and concluded that e.g. Kubernetes on GCP works a lot better than on either AWS or Azure?
- deleted 8y ago
  [deleted]
taeric 8y ago
Agreed, though, as a sibling said, making a habit of dropping a ton of features constantly is annoying. Especially when there were options before. If I liked an old version of a native application, used to be I could just keep that old version for a long time. Especially if it was isolated in functionality, even the security implications weren't that dangerous. Now, everything needs everything. And with the web, you can't pin a version to where you like it. :(
pmikesell 8y ago
I was, almost daily. It was a nice tool.
wetpaws 8y ago
It was one of the few google products that was critical for me that I used daily both through web interface and 3rd party app integration. I understand "not used by me = not used by anyone" fallacy, but it can be applied to any product closed by google, including reader, inbox, talk, etc.

5 ms·

Was anyone really using this feature? Even the author sounds like he wasn't actively using the feature. He entered some data 6 years ago, and went back today to

by rgbrenner 8y ago

tomohawk 8y ago
Repeatedly destroying trust by dropping things and breaking things for people, is a bad idea.
- gboudrias 8y ago
  At this point Google projects are basically less reliable than hobby projects.
  - psergeant 8y ago
    But hey, come build your company on top of GCP!
    - stefano 8y ago
      Funny thing is, people are lining up to do just that. I think that's a symptom of an industry where following the hype is more important than long term stability.
      - runeks 8y ago
        Or maybe they’ve carefully weighed their options, and concluded that e.g. Kubernetes on GCP works a lot better than on either AWS or Azure?
- deleted 8y ago
  [deleted]
taeric 8y ago
Agreed, though, as a sibling said, making a habit of dropping a ton of features constantly is annoying. Especially when there were options before. If I liked an old version of a native application, used to be I could just keep that old version for a long time. Especially if it was isolated in functionality, even the security implications weren't that dangerous. Now, everything needs everything. And with the web, you can't pin a version to where you like it. :(
pmikesell 8y ago
I was, almost daily. It was a nice tool.
wetpaws 8y ago
It was one of the few google products that was critical for me that I used daily both through web interface and 3rd party app integration. I understand "not used by me = not used by anyone" fallacy, but it can be applied to any product closed by google, including reader, inbox, talk, etc.