Curly braces: An evolution of UNIX and C
The article discusses the evolution of curly braces in UNIX and C programming. It highlights the challenges faced in early computing environments, particularly with the Teletype Model 33, which lacked certain characters. The introduction of trigraphs and digraphs in C allowed for the representation of these missing characters, showcasing the adaptability of programming languages over time.
- ▪The Teletype Model 33 could not produce lowercase letters or curly braces, which were essential for C syntax.
- ▪C89 introduced trigraphs to represent missing characters, while C95 later introduced digraphs for better readability.
- ▪UNIX V4 implemented character translation to allow the use of curly braces on terminals that could not produce them.
2 outlets in our directory ran this story. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ Curly braces: An evolution of UNIX and C — r/programming
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Thalia Archibald’s blog |
| Canonical URL | https://thalia.dev/blog/unix-braces/ |
| Publication time | Thu, 21 May 2026 05:33:27 +0000 |
| Retrieval time | 2026-05-21T06:05:03.544Z |
| Last seen | 2026-05-21T06:05:03.544Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | dO9Ze_Ay5jw4 · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Thalia Archibald's blog Curly braces: An evolution of UNIX and C 19 May 2026 How were { } curly braces typed with a Teletype Model 33 on UNIX? These characters are especially important for C, but absent on this terminal. I was just asked a similar question 1 and in response, this is a tour of the coevolution of UNIX and C, from this perspective, featuring “hello, world” through the ages. This work is entirely my own (no AI) and the code samples are my construction. Sources for all inferences are cited. ASCII 1963 The Teletype Model 33 famously couldn’t write lowercase letters. This teleprinter was designed around the first edition of the ASCII standard, ASA X3.4-1963, which hadn’t yet decided lowercase was worth adding.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Thalia Archibald’s blog.
Discussion
0 commentsMore from Thalia Archibald’s blog
