4 ms·

That is because the Cider team did an amazing job of managing it, and spent tons of time going bug report by bug report to find and fix the blockers stopping pe

That is because the Cider team did an amazing job of managing it, and spent tons of time going bug report by bug report to find and fix the blockers stopping people from preferring Cider-V over Cider, instead of the typical Google deprecation approach of "monkey knife fight"

VirusNewbie 5mo ago
fucking lol, that is how it usually goes with deprecation.
computerdork 5mo ago
haha, that's a great way to put it! And I get the overall gist of it, but why monkeys? :)
- aleksiy123 5mo ago
  code monkeys
  - computerdork 5mo ago
    Don’t let them out of their cages, otherwise they’ll stop typing!
- InfiniteRand 5mo ago
  Because it's international waters
  - computerdork 5mo ago
    This is a very confusing but enlightened response. Will have to ponder on its true wisdom:)
    - siriusfeynman 5mo ago
      The phrase is a reference to an episode of the simpsons https://www.youtube.com/watch?v=RRdIltdDE4A https://www.youtube.com/watch?v=RRdIltdDE4A
      - computerdork 5mo ago
        Haha! Poor monkey, hope he ended up being okay:)
rossjudson 5mo ago
I came from storage, so the monkey knife fight there was between PARMs. Very entertaining. For storage engineering could basically say "Well, figure it out, because if you don't find XX capacity, Google will stop working. Like, all of it."
dmoy 5mo ago
I dunno, there's certainly a lot of monkey knife fight deprecations, but there's a lot that are handled pretty well. If we're talking about the source side of things, p4->piper/citc was done well. cs (get) -> grimoire was done well. I'd like to think we did a pretty good job of grokv2-> Kythe, though we did drop a few clients of grokv2 who were wayyyyyyy the fuck up xkcd/1172 creek (we did try to help them in the right direction, like offloading onto direct blaze depserver queries). I guess those are all close in the org to cider, so maybe that's just how dev infra deprecations used to go.

VirusNewbie 5mo ago

fucking lol, that is how it usually goes with deprecation.

computerdork 5mo ago

haha, that's a great way to put it! And I get the overall gist of it, but why monkeys? :)

aleksiy123 5mo ago
code monkeys
- computerdork 5mo ago
  Don’t let them out of their cages, otherwise they’ll stop typing!
InfiniteRand 5mo ago
Because it's international waters
- computerdork 5mo ago
  This is a very confusing but enlightened response. Will have to ponder on its true wisdom:)
  - siriusfeynman 5mo ago
    The phrase is a reference to an episode of the simpsons https://www.youtube.com/watch?v=RRdIltdDE4A https://www.youtube.com/watch?v=RRdIltdDE4A
    - computerdork 5mo ago
      Haha! Poor monkey, hope he ended up being okay:)

rossjudson 5mo ago

I came from storage, so the monkey knife fight there was between PARMs. Very entertaining. For storage engineering could basically say "Well, figure it out, because if you don't find XX capacity, Google will stop working. Like, all of it."

dmoy 5mo ago

I dunno, there's certainly a lot of monkey knife fight deprecations, but there's a lot that are handled pretty well. If we're talking about the source side of things, p4->piper/citc was done well. cs (get) -> grimoire was done well. I'd like to think we did a pretty good job of grokv2-> Kythe, though we did drop a few clients of grokv2 who were wayyyyyyy the fuck up xkcd/1172 creek (we did try to help them in the right direction, like offloading onto direct blaze depserver queries). I guess those are all close in the org to cider, so maybe that's just how dev infra deprecations used to go.