Each cell is intentionally terse. Where a project's exact capability depends on platform, radio, or build path, the cell says so rather than overclaiming. wfview details cross-checked against wfview.org, the user manual, and the project's GitLab README.
wfview is a single open-source desktop application written in C++ on the Qt toolkit. The codebase is the product: protocol support, UI, audio path, CW sender, and controller integration all live in one project. That is a clean shape for an open-source contribution surface and is one of the reasons wfview attracts a real volunteer community.
RigPlane is shaped as an open-core library plus a packaged desktop wrapper. The radio-control engine, transports, and protocol work live in rigplane-core on PyPI and GitHub under the MIT license. RigPlane Pro is the paid desktop app that wraps the engine with a packaged installer, license enforcement, and commercial support on top. Operators who want only the engine can pip install rigplane and use it directly; operators who want the packaged desktop experience pay for Pro. The two layers are deliberately separate.
The operators we hear from most often when they switch land on one of three reasons. First, they run mixed-vendor stations — an Icom HF radio next to a Yaesu portable or a Xiegu QRP rig — and they want one desktop and one config surface across all of them. wfview is primarily focused on the Icom protocol family (with growing Kenwood and Yaesu support), so a multi-vendor station can outgrow that scope. Second, they are developers or integrators building something on top of radio control, and an MIT-licensed Python library is structurally easier to embed than a GPL Qt application. Third, they want a paid product with a real support address rather than a community forum, even though the forum option remains perfectly legitimate.
None of those reasons reflect a deficiency in wfview. They reflect different operator profiles. wfview's volunteer maintainers ship a remarkably feature-complete project for free; if its scope matches your station, there is no good reason to pay for a commercial alternative. RigPlane Pro exists for the operators whose constraints are different — multi-vendor scope, embeddable library access, packaged desktop on macOS without a self-build, or a commercial support relationship.