Getting Started with Marlin

A high-performance stream and code editor that opens files nothing else will open.

Marlin Developer's Bench is a high-performance macOS and Linux plain-text and code editor built for the enormous files that make other editors freeze.

Marlin welcome sheet over the editor
New File ⌘N, Open Folder as Project ⇧⌘N, Open Demo Project, and Set Up Your Editor. The sheet says files and assistant context stay on this Mac.

The Visible Pipeline Philosophy

In traditional text editors, text transforms are one-shot modal dialogs: you configure a sort or regex filter, hit OK, the dialog vanishes, and all record of what occurred is lost.

Pipeline is a chain of steps on a source file. The steps are Match, Extract, Bucket, Sort, and Unique. Match keeps or drops rows by pattern. Extract splits each row into columns. Bucket groups rows by a key and counts them. Sort orders rows. Unique drops rows already seen.

The pipeline view says steps run as a stream, and nothing is written until you export. Write Result runs the full pipeline over the source and saves the result to a file.

Marlin pipeline view on access-small.log
Pipeline on access-small.log: 3,763 rows in, a step inspector with Match, Extract, Bucket, Sort, and Unique, and Write Result at the top right.

Large Files

The welcome sheet calls Marlin a plain-text editor for people who open 2 GB files and expect them to just open. Opening a huge file maps it and builds the line index off the main thread.

Marlin editing a server log
access-small.log in the editor. The tab strip keeps main.go, main.rs, and snapshot.mpk open beside it.

On This Mac

The welcome sheet says this is a sandboxed build, and that files and assistant context stay on this Mac. Diagnostics are exported only when requested. The settings footer reads Private local workspace.

Marlin Privacy settings
Settings, Privacy. No accounts, no analytics, no tracking. Marlin has no network entitlement, and every store it keeps is listed with its size.