linguist VS zig

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 🪄.

There is an issue proposing this approach: https://github.com/ziglang/zig/issues/4284

https://github.com/ziglang/zig/issues/224

e.g.:

> > When debugging/prototyping, it's useful to comment out a line without having to refactor, e.g.

When writing code in a scripting language, sometimes you need that extra bit of performance (or maybe an async feature from Zig).

NodeJS is by no means a slow runtime, it wouldn’t be so popular if it was. But compared to Bun, it’s slow. Bun was built from the ground up with speed in mind, using both JavascriptCore and Zig. The Bun team spent an enormous amount of time and energy trying to make Bun fast, including lots of profiling, benchmarking, and optimizations.

ntdll.dll!RtlUserThreadStart()

There are valid reasons to use APIs from NTDLL. Where I disagree with zig#1840 is the idea that it is always better to use NTDLL versions of API. Every other software ecosystem uses the standard Win32 APIs and diverging from that without a good reason seems like a good way to have unexpected behavior. One concrete example is most users and programmers expect Windows to redirect some file system paths when running on WOW64. But this is implemented in Kernel32, not ntdll.

https://github.com/ziglang/zig/issues/11894

Zig also has an IRC channel on libera (#zig) that is moderated by Andrew Kelley.[1]

[1] https://github.com/ziglang/zig/wiki/Community