glean VS linguist

We do what cargo-lipo recommends: Adjust the library search path per target, build your library as normal per target and Xcode will figure out the rest. That works perfectly fine. We ship our library as an xcframework within a Swift package now. Applications can then rely on the Swift Package Manager to do its thing. (At some point I should write this up nicely in a blog post or something I guess...)

Yup, NDK 21 works just fine. We've been using that in our Android projects for a long time now.

I suspect they'll just use Mozilla's very own telemetry SDK

I dunno if this interests you, but you actually have influence over the formatting of https://github.com/someengineering/fix-cf/blob/main/fix-role... via .gitattributes communicating to GH that it's actually yaml: https://github.com/github-linguist/linguist/blob/master/docs...

There’s already a draft pr for this: https://github.com/github-linguist/linguist/pull/6686

GitHub uses Linguist to

I have found that: https://github.com/github-linguist/linguist/blob/master/docs/troubleshooting.md, but I'm also currently not at home, so I will check it out later.

Another option is to use Linguist which is what GitHub uses (I use linguist via .gitattributes files for all of my code projects). It is community driven and supports essentially every language possible: see languages.yml.

Once you selected a topic you can further filter the projects by language. This means programming language as recognized by the linguist tool of GitHub. See what they say about repository languages

As I later found out, GitHub uses the Linguist library to measure the amount of lines written in a specific language... which is still pretty magic 🪄.