In one paragraph

This theme collects tools built for practitioners: people writing code, making generative art, auditing sites, or managing their desktop. p5.js brings the Processing sketch model to the browser. lighthouse audits web pages for performance and accessibility. goose designs a systems language around heap-free memory. unicel adds unit tracking to spreadsheet cells. awesome-microduck indexes robotics software for a specific hardware platform. pixl-put restores macOS windows to their saved positions. What counts here: languages, auditing tools, creative-coding libraries, and personal utilities for people who make software and things.

The main approaches

Creative coding

A library wraps browser drawing APIs behind a beginner-friendly function set. You write setup() and draw(), call geometry and sound functions, and publish directly to the web. Example: processing/p5.js.

Web auditing

A tool loads a page in a controlled browser session, collects performance and accessibility metrics, and reports scores with actionable findings. The gather and audit phases can run separately. Example: GoogleChrome/lighthouse.

Languages

A new compiled language makes a specific tradeoff at the design level. Goose eliminates the heap entirely, storing all dynamic memory on bump-pointer stacks, and emits a single C file you compile with any C compiler. Example: aardappel/goose.

Personal utilities

Small tools that fix a specific friction point on a developer’s machine. Unicel adds dimensional analysis to a spreadsheet. PixlPut saves and restores macOS window positions per Mission Control Space. Examples: jacksodj/unicel, aaronscribner/pixl-put.

Hardware

A curated index tracks software, simulators, trained policies, and datasets for a specific robot platform, with machine-readable registries for tooling. Example: joeynyc/awesome-microduck.

Map of the theme

flowchart LR
  t["Developer and creative tools"]
  t --> f1["Languages"]
  t --> f2["Web auditing"]
  t --> f3["Creative coding"]
  t --> f4["Personal utilities"]
  t --> f5["Hardware"]
  f1 --> r1["aardappel/goose"]
  f2 --> r2["GoogleChrome/lighthouse"]
  f3 --> r3["processing/p5.js"]
  f4 --> r4["jacksodj/unicel"]
  f4 --> r5["aaronscribner/pixl-put"]
  f5 --> r6["joeynyc/awesome-microduck"]

Where the new ideas are

aardappel/goose uses a heap-free memory model where all dynamic allocation uses bump-pointer stacks, making deallocation a single store and eliminating lifetime annotations. Nested data stays inline, enums can be sized per variant and relative references can be 1, 2 or 4 bytes; the README’s order record is 29 bytes in Goose against 160 in C++.

jacksodj/unicel treats every cell value as a (number, unit) tuple at the formula-engine level, so unit cancellation and metric/imperial conversion are first-class operations rather than manual conversions in separate cells.

GoogleChrome/lighthouse separates the gather phase from the audit phase, so you can capture browser artifacts once and re-run audits offline without hitting the network again.

joeynyc/awesome-microduck pairs a human-readable curated list with a versioned machine-readable policy registry and revocation list, so downstream tooling can consume the index directly.

Side by side

Repo	Approach	Language	Offline/local operation	Extensible	Output format
processing/p5.js	Creative coding	JavaScript	Not stated; runs client-side in the browser	Yes, community libraries	Canvas/WebGL in browser
GoogleChrome/lighthouse	Web auditing	JavaScript	Yes, gather once then re-audit offline	Yes, plugin API for custom gatherers and audits	HTML, JSON, CSV
jacksodj/unicel	Personal utilities	Rust	Yes, desktop app	Not stated	.usheet JSON, Excel export
aardappel/goose	Languages	C++ (compiler), emits C	Yes, TinyCC backend bundled	Not stated	Single C file
joeynyc/awesome-microduck	Hardware	JavaScript	Not stated	Yes, structured submission form	Markdown list, policies.json, revocations.json
aaronscribner/pixl-put	Personal utilities	Swift	Yes, data stored locally in ~/Library	Not stated	Local capture files

How the idea moved

flowchart LR
  n1["started Feb 2013<br/>processing/p5.js"]
  n2["started Mar 2016<br/>GoogleChrome/lighthouse"]
  n3["started Oct 2025<br/>jacksodj/unicel"]
  n4["started Aug 2026<br/>aardappel/goose"]
  n5["started Aug 2026<br/>joeynyc/awesome-microduck"]
  n6["started Oct 2026<br/>aaronscribner/pixl-put"]
  n1 --> n2 --> n3 --> n4 --> n5 --> n6

• started Feb 2013 · p5.js · Adds: Brings the Processing setup/draw sketch model to the browser with global mouse variables, p5.sound, WebGL, and a hosted web editor, lowering the barrier to creative coding on the web.
• started Mar 2016 · lighthouse · Adds: Audits web pages for performance, accessibility, SEO, and best practices in a throttled Chrome session, with a separated gather/audit architecture that allows offline re-auditing from saved artifacts.
• started Oct 2025 · unicel · Adds: Stores spreadsheet cell values as (number, unit) tuples so unit cancellation, dimensional errors, and metric/imperial conversion are handled by the formula engine, with SQL queries, Excel export, and MCP integration.
• started Aug 2026 · goose · Adds: Provides a heap-free compiled systems language where all dynamic memory lives on bump-pointer stacks, enums can be sized per variant, and references stay valid without lifetime annotations, emitting a single C file.
• started Aug 2026 · awesome-microduck · Adds: Indexes software, simulators, trained policies, datasets, and hardware resources for the Microduck robot, with sim-only labels and a versioned machine-readable policy registry for tooling consumption.
• started Oct 2026 · pixl-put · Adds: Saves and restores macOS window positions per Mission Control Space, identifying each window by workspace path or document, and by browser tab URL when you turn that opt-in setting on, rather than just its application.

Easily confused

This theme can look like a general “open source tools” dump. The difference is scope: everything here is built for or by developers and makers, either to improve their workflow (window management, spreadsheet unit tracking), to produce creative output (generative graphics), to evaluate what they ship (web auditing), or to define how they write code (language design). A generic productivity app or end-user consumer tool would not belong here.

The robotics entry (joeynyc/awesome-microduck) might seem out of place, but it fits because it is an index of software and simulation tools aimed at people building and training robot behaviors, not at end users.

Gaps nobody has filled

• Nothing here measures runtime correctness or test coverage for the creative-coding or personal-utility tools.
• No tool addresses cross-platform window management; PixlPut is macOS-only and needs yabai with System Integrity Protection partly disabled to move windows between Desktops.
• The web auditing tool (Lighthouse) covers browser-rendered pages but nothing here audits native desktop or CLI application interfaces.
• Unicel saves local .usheet files and exports one-way to Excel; its README describes no collaborative editing or sync.
• Lighthouse checks lang attributes and hreflang links, but nothing here checks translation quality or locale coverage of a site’s content, even though p5.js documentation is available in multiple languages.