WHAT? That is crazy talk. JACK is the most complected audio setup I have ever worked with. I owned a Record Label and a small studio. If you have to setup JACK from scratch it can get crazy complicated. Once you get it working it is an AWESOME framework but I only would ever see people needing low latency to ever really use it.
JACK is 100% for a DAW (Digital Audio Workstation) and it is for low latency. Pulse is for the rest. I have found that the legacy of a poor initial deployment has been a heavy chain around its neck just like KDE 4, RPM (for having an issue for a few months over 10 years ago) and now Systemd (Systemd had a fine performance roll-out but philosophy issues).
/usr/lib/pulse-11.1/modules/module-jack-sink.so
/usr/lib/pulse-11.1/modules/module-jack-source.so
/usr/lib/pulse-11.1/modules/module-jackdbus-detect.so
I can use pavucontrol with ease to redirect an application's audio output (e.g. chromium's) to the jack sink.It's a painful process to accomplish the same thing without using pulseaudio, because you're going to have to mess with ALSA configuration files- and believe me, that's no fun at all.
In other words, I don't need no stinking' "game/consumer Audio", which is what Pulseaudio represents to me ..
Therein lies the beauty, I guess, of Linux - and of F/OSS creative-tools, in general ..
In that case, you can also chose hardware that works well with PA, so I don't see JACKs benefit there. Also, I don't think they're equivalent in functionality.
However, its moot - this is not consumer audio. Its more, "studio production audio"...
You probably won't have to. I think the long term plan is for Pipewire to replace PulseAudio (and be an alternative to JACK). Pipewire also does video. The initial release of Pipewire is video only with audio support to come:
https://blogs.gnome.org/uraeus/2017/09/19/launching-pipewire...
No that's not it at all. It's a framework that will use Pulseaudio OR Jack. Jack is only for low latency needs AKA Professional audio production.
"Pipewire is used to build a modular daemon that can be configured to: be a low-latency audio server with features like pulseaudio and/or jack.
Why not fix what we have rather than yet another rewrite with all its attendant exciting bugs.
So, just as a counterpoint, I'm guessing you're a Pulseaudio user ..