Ported freetype, fontconfig, harfbuzz, and graphite to Fil-C

A dev claims his “memory‑safe Linux” finally looks good after porting the big font squad — FreeType, Fontconfig, HarfBuzz, and Graphite — to Fil‑C, a safety‑minded take on the C language. He shows off Deja Vu monospace and swears it’s snappy enough for daily use. Cue the crowd: half clapping, half clutching their popcorn.

The hottest take? Skeptics asking, “What’s the catch?” One commenter warns that claims of memory safety without rewriting code will get the Rust and Zig faithful sharpening knives. Another asks if every program has to be recompiled and whether Fil‑C “rewraps” system calls like Go — a polite way of saying, explain the fine print.

Then comes the horror story: a reader recalls digging into Fontconfig and finding code that looked like a classic “use‑after‑free” (a bug where software touches deleted memory), saved only by an undocumented incref — basically a secret extra step keeping data alive. The community turned that into a meme: “Undocumented incref is my co‑pilot.” Others joked, “Pretty fonts don’t fix ugly crashes,” while fans countered with, “Safe and stylish is the vibe.” It’s fonts, safety, and a full‑blown comment‑section cage match — and we’re here for it.