Pros and cons

Pros

• Quick and immediate setup: it is “easy to get up and running” compared to more complex alternatives.

• Free.

• It does not “throw out” random characters when listening to noise (compared to other decoders).

• Decent word spacing and, in some cases, less “stuck-together” text.

• Waterfall/spectrum and signal selection: the project page highlights automatic tracking, manual selection, and a narrow DSP filter (about 80 Hz) for a stated speed range.

• Practical use with receiver/WEBSDR: a “simple” option together with CWGet and FLdigi, provided you take good care of the audio chain and filters.

Cons

• “Hunting” when the signal drops or stops: as soon as the CW breaks off or becomes slow/irregular, the program tends to look for other signals and this can dirty the decoding; when two nearby signals are present it can “bounce” between them.

• Intrinsically variable reliability (not “only” a software issue): human operators, QRM/QRN/QSB, wide filters, or adjacent signals can throw any decoder off; decoding can be hit-or-miss and requires a narrow CW filter + correct audio level.

• Dependence on a properly set audio chain: with WEBSDR + a virtual audio cable, you may get “random” decodes or have difficulty correctly centering the peak/tone.

• Outdated software: the project page indicates a 2016 release (v1.0.0.5) and .NET requirements, so there is a risk that on modern PCs / “locked-down” environments you may need workarounds or compatibility fixes.

Practical usage note
If you try it via radio or WEBSDR, the tips:

• Use the receiver in CW mode with the narrowest filter possible.

• Adjust tone and audio level properly (neither too low nor saturated).

• If there are CW signals very close to each other, expect confusion: it is not a rare case.