Reading the sibling comments, I realized that GitHub and SG have built tooling to index text, while Google have built tooling to index C++. cs.chromium et al e

Reading the sibling comments, I realized that GitHub and SG have built tooling to index text, while Google have built tooling to index C++. cs.chromium et al experiences instantaneous dropoff from "wow this is kind of amazing" the moment you start wading through JavaScript or Mojo glue code. Here's the JS source of the dino game; notice how you can't click anything: https://source.chromium.org/chromium/chromium/src/+/main:components/neterror/resources/offline.js https://source.chromium.org/chromium/chromium/src/+/main:com... A quick Google for "most popular languages on github" just found https://madnight.github.io/githut/ https://madnight.github.io/githut/, which (if it's correct) reveals that GitHub's most popular language (by commit activity) is Python (17%), very closely followed by JavaScript (14%). Then you have Java (12%), TypeScript (8%), Go (8%), C++/Ruby (both 6%), and PHP (5%). So on GitHub C++ apparently represents 6% of PR activity, while the top two languages (Python/JS) which represent 31% of PR activity are not only interpreted but also dynamically typed. Which tells a very interesting story about the benefits of being able to generate an AST with type information: you can scale insight that much more broadly and deeply. :(