I recently became aware that Nova (Panic’s next gen replacement for Coda) has been out since September, and decided to give it a quick spin.
Now, I’m currently working on an internal IDE that runs in Chrome so this is of special interest to me. In particular, I was wondering if Panic had come up with new magic sauce to advance the “state of the art” in lightweight platform-native IDEs, the way they did when they first shipped Coda.
I remember my first complaint about Coda was that its CSS editing tools were not up-to-par with CSSEdit, which Cabel (who has been known to reply to questions and suggestions directly) said was something they’d hoped to license, but ended up having to do themselves. (Turns out the CSSEdit people were working on Espresso, an ambitious and interesting but perpetually not-quite-there yet Coda rival.) Anyway, Coda’s CSS tools eventually got decent, but never caught up with CSSEdit.
Luckily, I became so ridiculously fluent in CSS (which I’d rate as the second-hardest language to learn that I’ve learned, after regular expressions) that I’ve not really needed anything beyond a basic text editor in years. (At the time, I regarded CSS with confusion and disdain and hoped to learn as little about it as possible.)
Anyway, some quick observations:
- It’s beautiful. Yay.
- It seems very much like a native vscode. Yay.
- It’s not interoperable with vscode extensions (and that’s likely very hard to do) and I haven’t looked into how hard it would be to “port” an extension from vscode. Boo.
- It doesn’t appear to leverage existing quasi-standards, the way Sublime leveraged TextMate stuff, and vscode leverages… stuff. Boo.
- It doesn’t handle terminals as gracefully as vscode. vscode’s terminal by default appears as needed, at the bottom of the main window, and tucks itself into a tiny space with a click. Boo.
- Running node package scripts is clunky (it requires a third-party extension that isn’t nearly as nice as what vscode has gotten me used to; of course vscode recently removed it). I don’t want Panic to over-focus on node users, because Coda’s over-focus on PHP users is one reason I stopped using it. Still, boo.
- Nova supports themes. Not a surprise. I couldn’t quickly find documentation on how to create a new theme, but I imagine it won’t be terribly difficult and it will be feasible to convert themes from other popular things to Nova. Meh.
- Nova lets you theme its overall UI, code editors, and terminals separately! This is awesome, since it allows you to easily differentiate panes at a glance, rather than everything looking pretty much identical. Yay.
- I was disappointed, when trying to open a Remote Project, that it does not automatically (or with a click) imports server settings from Transmit, of which I have been a user since 1.0). I had just made a quick fix to one of my demos using Transmit, which let me open (i.e. log into) the server, open the file (on the server) directly with BBEdit, make the fix, hit save the way I would for a desktop file, and reload the site to check the fix worked — that’s the workflow it needs to at least match. Boo.
Nova renders color swatches on the line-count column as opposed to the way vscode does it (inline in the text, somewhat disconcertingly). In both cases you can click to get a color-picker, but Nova’s is much nicer (it has spaces for you to keep common colors, for example, but seriously — use css variables!).
This is nice, but I don’t see any assistance for things like setting fonts, or borders. Although I have a license for Espresso somewhere or other, I’m not going to reinstall it just to take a screenshot, but here’s a capture from their website (yes, it lives!):
The user’s cursor is in a rule, and in addition to the text, the values are exposed as the UI shown above. This is basically a tiny part of what CSSEdit was doing, over ten years ago — my receipt for CSSEdit 2.5 is dated 2007. CSSEdit also allowed you to open a web page, edit its underlying styles live, and then save those changes directly to the sources, kind of like a better and automatic round-trip version of the workflow many of us use in Chrome/Safari/Firefox using the Elements panel.
The first extension I tried to use was from standardjs, which I love. I didn’t notice this until later:
This is not good. It reminds me of Lotus Notes telling me it needs me to do five specific things to do what I obviously want to do. Automatically loading dependencies is kind of a solved problem, and a stupid hassle to do yourself, these days… Boo.
It’s hard to compete with a free tool that’s backed by Microsoft. And vscode has become a lot of people’s, especially web-developers’, preferred editor. It’s easy to see why. Because any web developer must pretty much know all the tech that underlies vscode, it has a particularly rich extension library.
Jetbrains suite of java-based tools has also earned a huge following. (Sublime Text—once seemingly everyone’s favorite editor—hasn’t received an update since 2019. The team seems to have switched their focus to Sublime Merge.)
Overall, my initial reaction to Nova is slightly more negative than positive. I’m sorry to say this but I’m unconvinced.