it’s a build system itself, it doesn’t need make or whatever and compilation speeds are similar to ninja – which means it can do things like distributed building – and implement local caching, like ccache but supporting msvc as well as gcc/clang (actually msvc might be disabled at the moment) – … likewise remote caching, like Mozilla’s sscache for teams (again supporting msvc/gcc/clang)

So it offers nothing over cmake, and at best it matches features already offers for ages, such as transparent support for compiler cachês and distributed compilers.

it has its own package manager but also works with pretty much all other popular package managers –

That lies somewhere between matching cmake's features, and placing users in a losing proposition with its own package manager.

can configure project with a TUI menu xmake f --menu

Not only is this irrelevant but it is also something cmake provides.

Also, cmake is the de facto standard and supported natively by IDEs such as Visual Studio.

Knowing this, why would anyone bother with xmake?