So there is definitely a use case, it’s just maybe not for you
> very few use cases
The average person is not compiling programs or dealing with Kubernetes.
Don't get me wrong, they still work amazingly well for games. It's just that they sacrificed some performance in those chips for the higher core count so it only makes sense they'd want to push that further.
But my guess is they don't want to compete with their threadripper line. Unfortunately those come much later in the product cycle so we'll probably be waiting some time for a Zen 4 threadripper.
Ideally, portage would take memory (including ramdisk) requirements of packages into account when scheduling builds (some packages do check for free memory) and ask as a make jobserver [0] (with patches for non-make build systems to support jobservers) to always fully use the available resources.
[0] https://www.gnu.org/software/make/manual/html_node/Job-Slots...
There is also little doubt that AMD Raphael will be better than Intel Raptor Lake at multi-threaded tasks, even if they now have the same number of threads. The reason is that AMD is made with the much more efficient TSMC process and the consequence is that at equal power consumption the AMD CPUs will reach much higher clock frequencies.
This is the essential difference between single-threaded and multi-threaded tasks, during the former the performance is limited by the maximum turbo clock frequency, while during the latter the performance is limited by the clock frequency at a fixed power consumption, which depends more on the manufacturing process than on the microarchitecture of the CPU.