5 ms·

The current internal CodeSearch is one of the best tools available for Google engineers. It's really a marvel.

tehlike 7y ago
Code search, critique, Piper/citc/cider are amazing for developing Power drill is fantastic for drilling down data. So much money was made thanks to this one.
- ignoramous 7y ago
  Are these code tools built using https://github.com/kythe/kythe https://github.com/kythe/kythe ? Any other OSS projects by Google that back these?
  - cameronbrown 7y ago
    I believe so. Kythe seems to have spawned out of the internal CodeSearch.
  - hangtwenty 7y ago
    Something that is not by Google but which you would probably like - SourceGraph. Has commercial options but it is OSS. https://about.sourcegraph.com/ https://about.sourcegraph.com/
- dvirsky 7y ago
  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.
jules 7y ago
Do you have a list of all major Google tools and why they're better than what's available elsewhere? (if so)
- cameronbrown 7y ago
  :) https://github.com/jhuangtw-dev/xg2xg https://github.com/jhuangtw-dev/xg2xg
- antoinealb 7y ago
  In my opinion, what makes them really great is the tight integration that they have. For example, since the whole company uses one build system and one single repository, you can build a truly awesome IDE that knows about every library in the company and can autocomplete for it. Same for code search, where cross references are accurate and work cross languages (for example a class generated from Protobuf).
  - londons_explore 7y ago
    Outside Google, the percentage of my coding time I spend hunting some dependencies source tree for the relevant header files or documentation or "Where on earth is this constant defined" is huge. With codesearch, answering those kind of questions is near instant.
- dvirsky 7y ago
  So CodeSearch, Critique, Borg, Sherlog, Cider come to mind as top notch tools that are not available outside. As far as libraries go, the C++ Fibers thing is incredible and I don't think it's open. Blaze is amazing (albeit a bit slow) but Bazel should be more or less the same, haven't used it. Dremel, Spanner, Tensorflow, Proto, grpc are all available outside. Abseil (https://abseil.io/ https://abseil.io/) is a great library available to everyone.

Code search, critique, Piper/citc/cider are amazing for developing Power drill is fantastic for drilling down data. So much money was made thanks to this one.

ignoramous 7y ago
Are these code tools built using https://github.com/kythe/kythe https://github.com/kythe/kythe ? Any other OSS projects by Google that back these?
- cameronbrown 7y ago
  I believe so. Kythe seems to have spawned out of the internal CodeSearch.
- hangtwenty 7y ago
  Something that is not by Google but which you would probably like - SourceGraph. Has commercial options but it is OSS. https://about.sourcegraph.com/ https://about.sourcegraph.com/
dvirsky 7y ago
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.

jules 7y ago

Do you have a list of all major Google tools and why they're better than what's available elsewhere? (if so)

cameronbrown 7y ago
:) https://github.com/jhuangtw-dev/xg2xg https://github.com/jhuangtw-dev/xg2xg
antoinealb 7y ago
In my opinion, what makes them really great is the tight integration that they have. For example, since the whole company uses one build system and one single repository, you can build a truly awesome IDE that knows about every library in the company and can autocomplete for it. Same for code search, where cross references are accurate and work cross languages (for example a class generated from Protobuf).
- londons_explore 7y ago
  Outside Google, the percentage of my coding time I spend hunting some dependencies source tree for the relevant header files or documentation or "Where on earth is this constant defined" is huge. With codesearch, answering those kind of questions is near instant.
dvirsky 7y ago
So CodeSearch, Critique, Borg, Sherlog, Cider come to mind as top notch tools that are not available outside. As far as libraries go, the C++ Fibers thing is incredible and I don't think it's open. Blaze is amazing (albeit a bit slow) but Bazel should be more or less the same, haven't used it. Dremel, Spanner, Tensorflow, Proto, grpc are all available outside. Abseil (https://abseil.io/ https://abseil.io/) is a great library available to everyone.