Skip to content
← All work

01SYSTEM.OUT.PROTOCOL/Open Source

HELLO WORLD UNIVERSE

A visual and technical anthology of computational history across programming languages.

Role
Open Source Creator & Maintainer
Stack
Next.js / TypeScript / MDX / TailwindCSS
Year
2026
Status
Open Source

01Context

A centralized, structured reference for the origin syntax, execution models, and compiler idioms of historical and contemporary programming languages.

02Problem

Most language syntax references are either dry text listings or fragmented across wikis. The goal was to build a curated, statically pre-rendered technical showcase where each language's snippet, execution semantics, and memory model are explored.

03Constraints

  1. 01Zero runtime database dependencies for instantaneous edge delivery
  2. 02Strict static compilation (SSG) for all language entries
  3. 03High typographic precision for monospaced code blocks across desktop and mobile viewports

04Architecture

A content-driven Next.js application utilizing typed MDX documents compiled at build time into static HTML pages with zero client-side fetching waterfalls.

Content Pipeline
Structured MDX files parsed via gray-matter with custom remark/rehype syntax highlighters.
Language Registry
Typed TypeScript registry validating execution paradigm, author, release year, and compilation target.
Code Render Engine
Accessible code viewer with line numbering, copy mechanics, and semantic token styling.

05Decisions

D1MDX Static Generation instead of headless CMS

Why

Language definitions are versioned alongside code in git, eliminating external network latency and rate limits.

Result

Instant page transitions, offline preview capability, and simple contribution workflows.

D2Custom token formatting rather than heavy third-party code block embeds

Why

Keeps client bundle size minimal while matching the custom brutalist aesthetic of the site.

Result

Fast First Contentful Paint (FCP) and no third-party script blocking.

06Trade-offs

Pure static build vs live code execution backend

Gained

  • +Infinite scaling on edge CDNs
  • +Zero security attack surface for untrusted code execution

Gave up

  • −Users cannot run arbitrary code interactively in-browser without integrating WebAssembly runtimes

07Performance

  • ↯100% static HTML generation during build step
  • ↯Zero third-party telemetry or runtime analytics dependencies
  • ↯Sub-100ms global Time-To-First-Byte (TTFB) via edge deployment

08Challenges

  • #Structuring syntax highlighting tokens consistently across languages spanning 60+ years (from Fortran/COBOL to modern Zig and Rust)
  • #Maintaining responsive mobile layouts for long, unformatted historical assembly instructions

09Learnings

  • →Static site generators excel when the data structure is treated as an immutable schema rather than loose markdown files.
  • →Designing monospaced layouts requires strict vertical cadence and careful overflow-x containment.

10Retrospective

Integration of WebAssembly-based micro-compilers (e.g. Pyodide, QuickJS, and Rust Wasm) would provide an optional client-side REPL for runnable languages without introducing a server backend.

Next project · 02

AMAR PRITHIBI →

A Minecraft-inspired procedural 3D voxel sandbox engine built from scratch in Three.js and WebGL.

AMAR PRITHIBI Thumbnail