aiuto

5 ms·

1.
by aiuto 4mo ago
> There's more history than this LOL. Understatement of the year, Laurent. :-)
2.
by aiuto 4mo ago
> Over time, engineers realize that Code Search is more important than their IDE. You nailed it. One particularly hard problem Google faced w.r.t. IDE integration was the intersection of thousands of RPCs defined by protobuf declarations
3.
by aiuto 4mo ago
+1. CitC and it's relationship to version control (perforce/piper) is central to all development. Let's say there were 100M file in the monorepo (an underestimate). You obviously never want to do a git clone of that. But what
4.
by aiuto 2y ago
That is missing the point about the misdirection of costs. Your suggestion forces the people doing meaningful semantic changes, into involuntary servants to the goal of cleaning the stylistic problems. It's fine to have a policy that c
5.
by aiuto 2y ago
I want to start by saying that I do not want to diminish or disparage the work that Russ, Rob, Laurent, and others have done. It has made the Google code base better. That is an inarguable fact. Nor do I want to pick on buildifier or gofmt
6.
by aiuto 7y ago
Being written in Java is essentially a non-issue. Bazel ships as a binary that self-extracts a JRE for its own use. You don't have to install Java unless you want to build Java apps. The real issue for highly reusable products like Qt
7.
by aiuto 7y ago
The cottage industry is already springing up. There are a few firms offering Bazel consulting and training. https://bazel.build/experts.html