The toolkit: languages and editors

← Album index · Edizione italiana

TEAM 03 · 6 STICKERS

Programmers need languages, editors and libraries. Meet the people who made other developers’ work more accessible, expressive and shareable.

Catalogue numbers, not a ranking. Skills are educational readings of the work, not personality judgements. Software is built by communities: every name also represents a network of collaborators.

STICKER 013 / 024 · 1989–1991

Portrait of Guido van Rossum
Kushal Das · CC BY-SA 4.0 · Wikimedia Commons

Guido van Rossum

Readability designer
Python

Contribution. Designed Python at CWI from late 1989; the first public release arrived in 1991. The language favours readable code and general-purpose use.

Skill to learn. Reduce friction between thought and program.

Legacy and context. Python and its communities support automation, research, education and applications. Libraries have their own licences.

Read the card’s source

STICKER 014 / 024 · 1987

Portrait of Larry Wall
Randal Schwartz from Portland, OR, USA · CC BY-SA 2.0 · Wikimedia Commons

Larry Wall

Text craftsman
Perl

Contribution. Created Perl to tackle practical processing and automation problems. The language became an important tool for system administrators and text processing.

Skill to learn. Expressiveness and attention to real problems.

Legacy and context. Perl, its modules and community made many solutions reusable. Perl and Raku are now distinct languages.

Read the card’s source

STICKER 015 / 024 · 1995

Portrait of Yukihiro Matsumoto
Christopher Adams · CC BY 2.0 · Wikimedia Commons

Yukihiro Matsumoto

Expressiveness designer
Ruby

Contribution. Created Ruby, an object-oriented language released in the 1990s. Its design centres the experience of the person writing the program.

Skill to learn. Care for the enjoyment and clarity of work.

Legacy and context. Ruby provides a free foundation for tools and applications. Ruby on Rails is a separate project and must not be attributed to Matz.

Read the card’s source

STICKER 016 / 024 · 1990s

JC

Typographic card: no attributed portrait.

James Clark

Reusable component builder
Expat · groff · XML

Contribution. Created Expat, a library for parsing XML documents, and tools including groff. He was also technical lead of the W3C group that produced the XML specification.

Skill to learn. Build small, reusable foundations.

Legacy and context. A library can support many programs without being visible to end users. Expat is maintained by a community.

Read the card’s source

STICKER 017 / 024 · 1991

Portrait of Bram Moolenaar
Sebastian Bergmann from Siegburg, Germany · CC BY-SA 2.0 · Wikimedia Commons

Bram Moolenaar

Editor craftsman
Vim

Contribution. Created Vim and guided its development for decades. He connected the project with charityware, inviting support for children in Uganda.

Skill to learn. Long-term care and everyday usefulness.

Legacy and context. Vim shows how a free editor can grow through extensions and contributions. The project continues beyond its creator.

Read the card’s source

STICKER 018 / 024 · 2005

Portrait of Audrey Tang
Camille McOuat · CC BY 2.0 · Wikimedia Commons

Audrey Tang

Language experimenter
Pugs · Perl 6 / Raku

Contribution. Started Pugs, an experimental Haskell implementation of the language then called Perl 6, now Raku, involving a community of contributors.

Skill to learn. Learn through shared prototypes.

Legacy and context. Pugs contributed to language experimentation; it is not the name of the widely used Raku implementation Rakudo.

Read the card’s source

Connections between cards: Unix → BSD and GNU; GNU + Linux kernel + other components → distributions; languages + libraries + servers → web services. Arrows indicate historical and technical relationships, not a single code lineage.

Nominate a new sticker

Who is missing from this team? Suggest programmers from any country, including less-known contributors, with work and sources. You can also use this form to correct a card. Suggestions are reviewed by the editor and are not published automatically.

Name and email are optional. Details are used to review your nomination and follow up if needed; do not include sensitive data. Contact details are not intended for publication.

← Back

Thank you for your response. ✨

Browse the other teams

The roots: Unix, objects and networks · The freedom team: GNU, Linux and communities · The toolkit: languages and editors · Our shared network: the Web, data and collaboration

Leave a comment

Your email address will not be published. Required fields are marked *