4 ms·

That is the most hideous source control system ever. Do they really need to be developer hostile just because Github is owned by Microsoft? I mean seriously,

That is the most hideous source control system ever. Do they really need to be developer hostile just because Github is owned by Microsoft? I mean seriously, who has time to commit to a project with a random set of tooling.

eropple 6y ago
I've never worked at Google, but I've used Gerrit not infrequently at jobs and on projects--it isn't "random" even if you've never run into it before. Gitiles is just a hat on top of it; it's not pretty but it is fast. It's not "developer hostile" to not use Github. Git works everywhere. It might mean that to contribute to an operating system a developer may have to learn how to use something that isn't Github, but honestly if that's a bar to contribution for somebody they probably weren't gonna anyway.
- deleted 6y ago
  [deleted]
ocdtrekkie 6y ago
Google uses GitHub for a bunch of things, I suspect it is more that the people working on it want to use Google's internal tooling as much as possible, and public user experience is considered less important than that.
- bun_at_work 6y ago
  This is the right answer. Google has tons of internal tooling and libraries and frameworks that are all just internal to Google.
  - kerneis 6y ago
    That may be true for Google in general, and internal code in particular, but that's definitely not the case for Fuchsia. We use the tools and interfaces available to the public to work on the code base: code search to browse the code, gerrit for reviews and monorail for tracking bugs.
mmastrac 6y ago
Welcome to the world of Building Large Google Projects. This is somewhat painful in the Android and Dart/Flutter world. I haven't tried building Chromium yet but I'm sure it's just as complex.
- moron4hire 6y ago
  Yeah, I've tried building Chromium on my own before. Chromium's build process is so inscrutable and changes so often that several Googlers I've talked to have said you can't really do it without handholding from another Googler in-the-know.
  - jmgao 6y ago
    Well, it could be worse: you could be building Chrome OS, which builds both Chrome and Android as part of its build.
  - snazz 6y ago
    git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git Add it to your PATH fetch --nohooks chromium && cd src ./build/install-build-deps.sh gclient runhooks gn gen out/Default autoninja -C out/Default chrome Congrats, you just built Chromium. Is it a different build process? Sure. But it sure isn't inscrutable, and they've been using this system for a while now.
- Lionga 6y ago
  Flutter/Dart is on Github
kerneis 6y ago
You may want to browse it using https://cs.opensource.google/fuchsia https://cs.opensource.google/fuchsia. Much nicer interface. (disclosure: I work on Fuchsia at Google)
- random3 6y ago
  Wow! That's so fast it feels good :) I'd actually prefer that as a default for GitHub. Is it based on a public tool? Does it render server-side?
  - kerneis 6y ago
    It is based on our Code Search tool, that is also used internally to index and browse most of Google's source code: https://developers.google.com/code-search https://developers.google.com/code-search The best part is the cross-references: try clicking on any identifier in https://cs.opensource.google/fuchsia/fuchsia/+/master:src/lib/files/file.h https://cs.opensource.google/fuchsia/fuchsia/+/master:src/li... for instance. I'm not sure how rendering works, I'm only a happy user :-)

eropple 6y ago

I've never worked at Google, but I've used Gerrit not infrequently at jobs and on projects--it isn't "random" even if you've never run into it before. Gitiles is just a hat on top of it; it's not pretty but it is fast. It's not "developer hostile" to not use Github. Git works everywhere. It might mean that to contribute to an operating system a developer may have to learn how to use something that isn't Github, but honestly if that's a bar to contribution for somebody they probably weren't gonna anyway.

deleted 6y ago
[deleted]

ocdtrekkie 6y ago

Google uses GitHub for a bunch of things, I suspect it is more that the people working on it want to use Google's internal tooling as much as possible, and public user experience is considered less important than that.

bun_at_work 6y ago
This is the right answer. Google has tons of internal tooling and libraries and frameworks that are all just internal to Google.
- kerneis 6y ago
  That may be true for Google in general, and internal code in particular, but that's definitely not the case for Fuchsia. We use the tools and interfaces available to the public to work on the code base: code search to browse the code, gerrit for reviews and monorail for tracking bugs.

mmastrac 6y ago

Welcome to the world of Building Large Google Projects. This is somewhat painful in the Android and Dart/Flutter world. I haven't tried building Chromium yet but I'm sure it's just as complex.

moron4hire 6y ago
Yeah, I've tried building Chromium on my own before. Chromium's build process is so inscrutable and changes so often that several Googlers I've talked to have said you can't really do it without handholding from another Googler in-the-know.
- jmgao 6y ago
  Well, it could be worse: you could be building Chrome OS, which builds both Chrome and Android as part of its build.
- snazz 6y ago
  git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git Add it to your PATH fetch --nohooks chromium && cd src ./build/install-build-deps.sh gclient runhooks gn gen out/Default autoninja -C out/Default chrome Congrats, you just built Chromium. Is it a different build process? Sure. But it sure isn't inscrutable, and they've been using this system for a while now.
Lionga 6y ago
Flutter/Dart is on Github

kerneis 6y ago

You may want to browse it using https://cs.opensource.google/fuchsia https://cs.opensource.google/fuchsia. Much nicer interface. (disclosure: I work on Fuchsia at Google)

random3 6y ago
Wow! That's so fast it feels good :) I'd actually prefer that as a default for GitHub. Is it based on a public tool? Does it render server-side?
- kerneis 6y ago
  It is based on our Code Search tool, that is also used internally to index and browse most of Google's source code: https://developers.google.com/code-search https://developers.google.com/code-search The best part is the cross-references: try clicking on any identifier in https://cs.opensource.google/fuchsia/fuchsia/+/master:src/lib/files/file.h https://cs.opensource.google/fuchsia/fuchsia/+/master:src/li... for instance. I'm not sure how rendering works, I'm only a happy user :-)