5 ms·

The most amazing thing to me about Cider-V was that Cider (without the V) actually went away after a relatively short amount of time, when virtually every other

by phreeza 4mo ago

The most amazing thing to me about Cider-V was that Cider (without the V) actually went away after a relatively short amount of time, when virtually every other internal service that is officially EOL-ed lives on essentially forever.

buildbot 4mo ago
It would be nice if they extended their external services the same behavior…
DannyBee 4mo ago
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 4mo ago
  fucking lol, that is how it usually goes with deprecation.
- computerdork 4mo ago
  haha, that's a great way to put it! And I get the overall gist of it, but why monkeys? :)
  - aleksiy123 4mo ago
    code monkeys
    - computerdork 4mo ago
      Don’t let them out of their cages, otherwise they’ll stop typing!
  - InfiniteRand 4mo ago
    Because it's international waters
    - computerdork 4mo ago
      This is a very confusing but enlightened response. Will have to ponder on its true wisdom:)
      - siriusfeynman 4mo 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 4mo ago
        Haha! Poor monkey, hope he ended up being okay:)
- rossjudson 4mo 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 4mo 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.
lunarboy 4mo ago
I feel like core dev team learned a lot about actually enabling a web based ide for line 100k engineers across the globe for a gazillion line mono repo. ciderv is really just a skin for the amazing infra. Which is also why I think there was less resistance to the change
thiagowfx 4mo ago
Initially I had thought so too. But later I realized that it’s quite easy to do so when you force-deprecate the old product. There was no real choice, the old IDE simply stopped working after a certain cutoff date. Adoption metrics felt forced and pushed, but were presented as if users were actively and willingly choosing the newer IDE.

by phreeza 4mo ago

buildbot 4mo ago

It would be nice if they extended their external services the same behavior…

DannyBee 4mo ago

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 4mo ago
fucking lol, that is how it usually goes with deprecation.
computerdork 4mo ago
haha, that's a great way to put it! And I get the overall gist of it, but why monkeys? :)
- aleksiy123 4mo ago
  code monkeys
  - computerdork 4mo ago
    Don’t let them out of their cages, otherwise they’ll stop typing!
- InfiniteRand 4mo ago
  Because it's international waters
  - computerdork 4mo ago
    This is a very confusing but enlightened response. Will have to ponder on its true wisdom:)
    - siriusfeynman 4mo 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 4mo ago
        Haha! Poor monkey, hope he ended up being okay:)
rossjudson 4mo 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 4mo 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.

lunarboy 4mo ago

I feel like core dev team learned a lot about actually enabling a web based ide for line 100k engineers across the globe for a gazillion line mono repo. ciderv is really just a skin for the amazing infra. Which is also why I think there was less resistance to the change

thiagowfx 4mo ago

Initially I had thought so too. But later I realized that it’s quite easy to do so when you force-deprecate the old product. There was no real choice, the old IDE simply stopped working after a certain cutoff date. Adoption metrics felt forced and pushed, but were presented as if users were actively and willingly choosing the newer IDE.