C had implementations, then there was a standard, then there were more implementations. At present we have GCC and clang as the preeminent “industrial strength” compilers and presumably MSVC is somewhere in the neighborhood of normal. A little curiosity will lead you to more recently commenced projects like <a href=“https://sr.ht/~mcf/cproc/” rel=“ugc”>cproc</a> and <a href=“https://github.com/Vexu/arocc/” rel=“ugc”>arocc</a>. On this very website you can find links to <a href=“https://duriansoftware.com/joe/the-lost-language-extensions-of-metaware’s-high-c-compiler” rel=“ugc”>tales of unusual C compilers and extensions</a>. And libc, in turn, is its own thing, cf. glibc, musl, and the BSDs. And yet I don’t feel like I’m scratching the surface of commercially relevant C toolchains that presumably contribute to making the C standardization process the agile and innovative workshop of good ideas we know today, nor the range of vendors who competed in the marketplace in the past. So, Lobsters, what are some lovable or infuriating C situations that you’ve encountered in your careers? What makes them special? What biodiversity still exists in weird corners of computing? Should I really be asking about Fortran?