4 ms·
While I'm a little annoyed by this (it seemed unlikely to me that GitHub would shut it down, so I actually used it), I can live with it. The "was only lightly d
by dataflow 4y ago
While I'm a little annoyed by this (it seemed unlikely to me that GitHub would shut it down, so I actually used it), I can live with it. The "was only lightly documented" comment is pretty unnecessary and just adds insult to injury though. What's that supposed to mean? It feels like such an "it's kinda your fault for putting too much faith in us" insinuation. GitHub literally blogged about the feature [1], did they expect people not to use it because it wasn't "heavily" documented? Should their users ignore their blogs from now on, because apparently it's an irresponsible thing to take their blogs at face value?
Oh, and I don't think they've sent anyone any notifications about this, like the repo owners. Not sure how people are supposed to find out; are all users expected to stay up to date with GitHub's blog... which GitHub is telling them not to trust?
[1] https://github.blog/2011-11-10-git-io-github-url-shortener/ https://github.blog/2011-11-10-git-io-github-url-shortener/
- math-dev 4y agoAll good points
- larusso 4y agoI’m in general not a fan of sunset ting services which are part of greater infrastructure. The demise of jcenter for instance is still hunting me because of cache misses etc. And I had the same thoughts about the documentation comment. For me this means that GitHub has put itself in the long lines of service companies who have no issues with pulling the plugs (because this is mostly the cheapest solution) of services they don’t want to maintain for whatever reason.
- ThrashBeard 4y agoThe way I understood "was only lightly documented" was they were blaming themselves like "we didn't put much work into it and didn't document it very well".
- hjkl0 4y agoAs someone without a leg in this race, I found the added context of “lightly documented” useful. It does help tell the story