Please see the updated version of this post here.
Preamble
Last year, I answered a question about which is "better" between Harlowe and SugarCube, see that response here. Harlowe has changed drastically in v3.2.x, so some of that information has become outdated.
Because the original response was somewhat frequently linked to, I wanted to update it for 2021. This post is that.
Introduction
You should try out the various options before settling on anything, it will probably be worth your time to do so. But overall, SugarCube is hard to go wrong with and easy to recommend and Harlowe has some issues and limitations that hold it back.
Chapbook and Snowman will not be addressed in this comparison, as they exist more on the margins, but they're worth trying out as well.
Comparison Between Harlowe and SugarCube
The core feature set is fairly similar. Harlowe has the thinner feature-set overall. It has more macros, but that doesn't tell the whole story, as Harlowe has a tendency to combine several macros together into a single one, or it will feature macros for basic data types or other simple operations, where SC will typically use JavaScript syntax. E.g., in Harlowe, you make an array with the array macro, (set: $arr to (array:)). In SC you instead use the literal, as you would in JS, <<set $arr to []>>.
For more on the specific diffrences in syntax and features, you can see this section of the SugarCube documentation.
It's also worth mentioning that Harlowe v3.2.x now features a toolbar with tons of features and functionality that can help new users write better code more easily. While this is a pretty neat idea, I don't think it changes much outside helping very new users get their foot in the door. Still, it's worth mentioning that the editing experience in the Twine 2 app is better in Harlowe between this toolbar and syntax highlighting, where to get similar features in SugarCube, you'll need to use a third party app, like VSCode (if you're interested, here's a great VSC extension).
That's just on the macro and markup side though. Harlowe completely lacks:
Any way to control the state history, which means longer Harlowe games will always start to lag and there's nothing you can do about it.
Audio support. (See below.)
Any configuration options in general. Harlowe is set up the way it is and any changes to its basic functionality typically need to be hacked into the engine.
Any JavaScript-facing APIs. You can leverage JavaScript code, but your code, by design, is never allowed to access Harlowe's engine. Even if you hack your way in, Harlowe is a field of rakes and its very easy to fuck up. (See below.) Update for 2021: this situation is markedly worse in 2021 as Harlowe macros no longer support any JavaScript at all, meaning useful methods and functions, and even patches and fixes and examples in the Twine Cookbook, are totally broken as of version 3.2.1. This does not appear to be a bug. This limitation makes Harlowe even less extensible, and makes certain bugs in the engine, like the bug that reloads maps as arrays, impossible to fix outside an official patch.
Because of the above, Harlowe is not really extensible. You can't really add functionality to the engine like new macros, and no sort of code extensions are supported by default. (I have created an unofficial framework that allows some interaction with Harlowe's engine from JS, but I stress that its built on hacks and dreams. See below for link.) Update for 2021: Harlowe now supports custom macros via a new macro. This feature is more similar to SugarCube widgets than true custom macros, but it is an improvement for sure.
Harlowe has no built-in features that help with code reuse other than the (display:) macro. There is no built-in way to reuse code by creating custom macros, widgets, or even really functions. It's a very tightly closed system. Update for 2021: As mentioned above, Harlowe now supports custom macros.
Harlowe is inexplicably not responsive. It would not be hard to make it responsive. It just isn't and no one knows why. Update for 2021: This continues to be an issue in 2021, inexplicably.
Harlowe has other problems, too:
Things like 1-based arrays and expressions that try to preempt errors you may have made introduce bugs and unexpected behaviors, and often don't help novices much to justify it.
Harlowe uses custom elements for everything. This means that without a rather sophisticated knowledge of the engine or of your browsers dev tools, adapting CSS you find online is challenging. Not great for a self-styled newb format.
Harlowe does not give a shit about performance. Everything is always deep cloned. Merely accessing an array causes it to be cloned, which makes basically every operation on any non-primitive data-type significantly slower than it should be. You can iterate over complicated data structures with thousands of entries with no noticeable performance impact in SC. If you try to iterate over a basic array of 100 elements in Harlowe you'll see it struggle to load the passage. Update for 2021: This situation is not improved in 2021, and certain new macros seem even more sketchy in terms of performance than before.
Bad ideas. I am not skilled enough to make something like Harlowe, but the way that (click:) style macros and the way the (event:) macro works are insane. They're these massive performance killers in a format that already has tons of performance issues, and doesn't let you configure it at all to alleviate any of them. That's a lot of sharp edges to give users.
Block-based elements render incorrectly. This seems like it will never be fixed. Update for 2021: Like with the lack of mobile support, this continues to be an issue.
I'm adding this in 2021, but it's been a problem since before the last post: when saved data is loaded as a part of session preservation or from a saved game, data maps are erroniously loaded as arrays. I wrote an unofficial patch that fixed this, but because Harlowe no longer allows JavaScript to be written in macros, that patch does not work on any versions of Harlowe higher than 3.2.x.
If it seems like I'm dunking on Harlowe, I am, but not because I don't like the format, more because I find it frustrating and I think its design is at odds with itself. It's fine for basic choice-based interactive fiction. SugarCube is designed for that too, but at least meets you halfway if you want a combat system or an inventory or resource management or random loot. Harlowe really doesn't, and if you want anything more complicated than some dynamic stuff here and there, you will be actively working against the format rather than with it.
In 2021, Chapbook is, in my opinion, a better option for a more limited, opinionated, and simple format, though be warned that it is even more limited in certain ways (though unlike Harlowe, it is extensible).
All that said, I do think trying both formats out is worth your time, and it may be worth it to try out Snowman and Chapbook too. Harlowe's hook based syntax is great to work with if you don't need anything beyond what it provides and you can deal with its foibles. And SC (and the other formats) are not perfect either, and I could come up with a pet peeve list for each if I wanted to. But I'd be lying if I tried to say the issues I have with Harlowe aren't more severe.
The "see below" stuff:
I have written an unofficial custom macro API for Harlowe: https://harlowe.twinelab.net/ Update for 2021: some features of this library may no longer work in v3.2.x and higher.
I've also created an audio library for Harlowe: https://hal.twinelab.net/ Update for 2021: some features of this library may no longer work in v3.2.x and higher.