Panic's Nova is a new macOS-only code editor — effectively Coda 3, but rebuilt deeply enough that the company gave it a fresh name. Its author, long settled into VS Code, spent time with the betas, bought a discounted license at launch, and has been using it on and off since. What follows is a working assessment rather than a review.

Prettier argument: what must carry over

VS Code is good, free, and what everyone on the team uses, so muscle memory is the real obstacle to switching. Two baseline conditions apply: nothing can be annoying at first contact — relearning is fine only after the transition — and something genuinely compelling has to justify it.

Prettier and Emmet are non-negotiable, and both exist as top Nova extensions.

I picked out a few I know I’ll want.

Emmet's default expansion is Ctrl-E and, as far as the author can tell, Tab expansion is not supported. All of Emmet's more advanced capabilities are present and remappable to any keys.

Key bindings

Binding setup holds up well. Familiar assignments carry over easily, including Command-T for "Open Quickly," the counterpart to VS Code's "Go to file…".

Sane defaults vs. an extension stack

One VS Code installation here carries nearly thirty extensions, each adding a small specific convenience, and none of them have been missed in Nova. The better outcome would be defaults good enough that fewer third-party fixes are needed beyond the two essential extensions. Case in point: indentation is already rainbow-colored without a plugin.

But notice the JSX isn’t particularly well highlighted even though it’s on the right syntax.

Search, and the trouble with being Mac-native

Find-in-project runs a dozen or more times a day, so it has to be strong. Results are good, but the editor often appears stuck on "Indexing Files…" — or at least feels stuck, because it gets the fan spinning.

Nova's Mac-ness is very pronounced. Narrowing find-in-project to, say, *.js files means creating a new search scope. Scopes can be saved under custom names, which is a neat idea, but the interface is as verbose and click-heavy as Finder's scope builder instead of a quick field where you just type *.js. It reads as macOS fidelity taking priority over usefulness.

Finder-style file navigation

Right-clicking a folder to open the file browser is exactly like right-clicking a folder in the Finder — comforting, since that menu is powerful. It also omits contextually useful entries; an "Open this folder in a terminal window" option is the notable one.

Interface polish

UI detail is handled well throughout: excellent coding-font selection, a minimap that renders code as little colored rectangles, and carefully crafted window and editor themes. It is all quite classy.

Coda lineage: SFTP and Panic Sync

Inheritance from Coda is still present, so remote server editing over SFTP is available. It proved handy recently for editing a file deliberately kept out of git — work that would otherwise have gone through Coda — and no setup was needed in Nova because Panic Sync carried over the authentication details.

That’s a remote file system.

The built-in browser and its rough edges

A built-in browser (Safari, of course) raises the question of whether the whole workflow — file browser, editor, terminal, browser, DevTools — can stay inside one application with minimal window juggling. The density of that layout is a lot to absorb at once, but it is appealing.

A Chromium option for the built-in browser would be welcome, since these DevTools are the more familiar set. The terminal also has a rough edge: a tmux session does not respond to click events.

Swift support

Curiously, Swift is not a built-in language. Given how Mac-native Nova feels, one would have guessed Panic wrote at least parts of it in Swift.

Notes on the landing page

If nothing else, nova.app is worth a visit for its CSS alone. The animated clip-path on the image showing Nova's themes is impressive — clip-path animations are reportedly hardware accelerated in Safari — and it is really just a set of stacked images sharing one staggered animation:

@keyframes wipe
{
    0% { clip-path: polygon(-50% 0%, 0% 0%, -50% 101%, -100% 101%) }
    100% { clip-path: polygon(150% 0%, 200% 0%, 150% 101%, 100% 101%) }
}

/* ... */

img#interface1 { animation-delay: -17000ms; }
img#interface2 { animation-delay: -15000ms; }
img#interface3 { animation-delay: -13000ms; }
img#interface4 { animation-delay: -11000ms; }

The <hr> is gorgeous too, and the page puts the display-p3 color format to work.

DevTools window showing CSS custom properties on the Nova landing page that reference display-p3 color values.