Programming language creators on GitHub

#	开发者	以什么闻名
1	Guido van Rossum @gvanrossum	Created Python in 1991, thirty years before most of today’s Python developers started using it.
2	Yukihiro Matsumoto @matz	Created Ruby and still leads its design as the language’s “benevolent dictator for life.”
3	Anders Hejlsberg @ahejlsberg	Turbo Pascal, Delphi, C#, and TypeScript - four languages apart, one career.
4	Graydon Hoare @graydon	Started Rust as a personal project before Mozilla, and later a foundation, took it on.
5	Rasmus Lerdorf @rlerdorf	Wrote the first version of PHP to track visits to his own online resume.
6	Brendan Eich @BrendanEich	Wrote the first version of JavaScript in ten days at Netscape in 1995.
7	Bob Nystrom @munificent	Created the Wren scripting language and wrote Crafting Interpreters, now a standard reference for building your own.
8	Martin Odersky @odersky	Created Scala after working on generics for javac - the same compiler most Java code still runs through.
9	Jeremy Ashkenas @jashkenas	Created CoffeeScript, which compiled to JavaScript and previewed syntax that later landed in the language itself.

Designing a language is a different skill than maintaining a popular library. A library has to solve one problem well. A language has to make ten thousand unrelated problems tolerable to solve in it, for decades, without the ability to take back a decision once enough code depends on it.

The people who have done this are a small group, and an unusually large fraction of them are still active on GitHub - not just as a formality, but reviewing issues, commenting on proposals, and occasionally still committing code to the languages they started.

Most of these started as someone’s side project

None of these languages began as an official initiative. Guido van Rossum wrote Python over a Christmas break. Rasmus Lerdorf built PHP to solve a narrow, personal problem and only generalized it once other people started asking for the code. Graydon Hoare built the first version of Rust on his own time before Mozilla decided it was worth funding.

This is worth remembering if you are evaluating a project by how it started: almost nothing that became foundational began with a roadmap. It began with someone annoyed enough by the available options to build a replacement for personal use.

Language design is a long game

Anders Hejlsberg has now shipped four major languages across four decades, each one shaped by lessons from the last. Martin Odersky spent years on Java’s generics implementation before designing a language that fixed what he saw as its limitations. That kind of compounding expertise doesn’t show up in a single repository’s star count - it shows up in the pattern across a whole profile.

If you’re looking at someone’s GitHub history to judge their design sense, look at the arc across projects, not just the size of the most recent one.

What this means for your own profile

Most developers will never design a language, but the underlying habit generalizes: the strongest profiles belong to people who kept building the thing that annoyed them, past the point where a smaller developer would have called it done.

You can see how contribution patterns actually look for long-running projects on their showcase pages, or generate the same breakdown for your own account.

Most of these started as someone’s side project

Language design is a long game

What this means for your own profile

Related reading