Dublin · Vol. IMMXXVI

QUILL

an editor that writes its own margins

No. 01 — The Morphing Editor

The Lead — A Feature

The page should know what you’re writing.

On development environments that stop pretending every task is the same task — and learn, at last, to morph.

Consider the toolbar. It greets you the same way each morning, whether you have come to chase a memory leak through a heap, to shape a small component, or to move a database from one schema to the next. It offers the identical row of icons for all three, as if the work were interchangeable. It is not.

A craftsman’s bench is arranged for the job at hand. The surgeon’s tray, the printer’s case, the chef’s mise en place — each is composed for one task and cleared for the next. Software, curiously, never learned this courtesy. It hands you every instrument at once and asks you to hunt.

Quill begins from the opposite premise. You tell it, in plain words, what you mean to do. It reads the room — the repository, the open files, the last error still warm in the log — and it composes an editor for that, and only that. The panels you need arrive; the rest never appear.

What remains is quiet. An interface with nothing to prove and nothing extra to show. It is built fresh for the task, and when the task is done, it is set aside — like a galley pulled after the page has gone to press.

One editor, observed in three states.

Plates i–iii

> debug a memory leak▍

  • Plate i.

    On debugging

    You ask to debug a memory leak. The page becomes a heap viewer.
    ·Heap — 1.8 GB
    ·Retained — worker.queue#7
    ·Last GC — 382ms
  • Plate ii.

    On composition

    You ask to write a React component. The page becomes a prop inspector.
    ·Props — tier, price, cta
    ·Variants — 5
    ·Storybook — synced
  • Plate iii.

    On migration

    You ask to migrate a database. The page becomes a schema diff.
    ·Changes — 3 tables, 1 index
    ·Reversible — yes
    ·Dry-run — green
Fig. 1 — The same environment under three intents. Debugging summons a heap viewer; a component summons a prop inspector; a migration summons a schema diff. No menu is hunted; the interface simply arrives composed for the work.

A Sidebar

How a sentence becomes an editor.

Four movements, from intent to rendered page, set below with hanging numerals.

  1. I.

    You type an intent.

    Plain language, the way you would describe the work to a colleague leaning over your shoulder.

  2. II.

    Context is compressed.

    The repository, its history, the open files, the last error — all distilled to a working set.

  3. III.

    The interface is composed.

    Panels, tools, and shortcuts are set like type, arranged for this task and no other.

  4. IV.

    It renders in 400ms.

    A fresh editor, printed to the screen, gone again the moment the work moves on.

Colophon

Set in Dublin. Built to listen.

An environment composed afresh for every task — and cleared the moment the work moves on.

Begin — No. 01free while the issue is in proof

or sign in to continue reading