Piper was actually a big source of frustration for me. Yeah it's dead simple, but once you have a CL chain, you're entering a world of pain. I've switched to Fig a while ago and haven't looked back. Beyond a tiny fix I'll start editing from CS or a throwaway citc client, it's just simpler to use fig. I've been able to juggle 4-5 CL chains easily and it makes my workflow much easier. Also splitting CLs before review is much simpler with Fig.
Re:How Google Code Search Worked (2012)
by ignoramous on Thursday March 12, 2020 @04:40AM
(#22554891)
Are these code tools built using https://github.com/kythe/kythe ? Any other OSS projects by Google that back these?
Re:How Google Code Search Worked (2012)
by cameronbrown on Thursday March 12, 2020 @06:40AM
(#22555418)
I believe so. Kythe seems to have spawned out of the internal CodeSearch.
Re:How Google Code Search Worked (2012)
by hangtwenty on Thursday March 12, 2020 @11:12AM
(#22557674)
Something that is not by Google but which you would probably like - SourceGraph. Has commercial options but it is OSS.
Power drill is fantastic for drilling down data. So much money was made thanks to this one.