C3's creator says calling it a "C alternative" was a marketing mistake

The creator of C3 published a post arguing that marketing the language as a "C alternative" was a fundamental error, because that phrase now signals a narrower set of use cases than he intended.

His reasoning is generational. He remembers C as an application language, back when Turbo Pascal and C were what you reached for on 16-bit home computers to write whole programs. Today, he writes, "C alternative" is read as "a programming language for what C is predominantly used for today" — OS development, embedded work, high-performance libraries and backends. People write databases in C, not video editors. So when he pitched C3 as "a C-like for people who like C," the audience heard systems programming, while he meant something closer to a replacement for the range from C through C++ to Swift.

The post also makes a design argument that explains the positioning. He blames a chunk of his own slowdown over the years on "methods first" thinking — game.run() rather than run(&game) — because binding behavior to an owning class forces architecture decisions up front and makes later restructuring expensive. He credits a procedural-in-practice PHP contract with showing him the object-oriented layers were never needed. C3 does have methods, he notes, mainly to avoid needing function overloading for things like foo.to_string(), which he concedes makes it harder to pull people out of that mindset.

He frames Zig's goal as replacing C where C is used now, and cites Odin as starting people in a better mindset. This is one designer's retrospective on his own project's framing, not a benchmark or a release; nothing in the post claims C3's implementation changes as a result.