The ability just to swap in the cuFFTW header for FFTW3's making calls execute on GPU (even though it doesn't give the best performance) is also nice for beginners.
> The last point is especially important if your host operating system is macOS, on which it is a really bad idea to directly install a binary Clang other than the one that comes with Xcode.
Why is this? I mean, I understand why you don't want to install over the system compiler, but having another version of Clang installed side by side shouldn't be an issue, should it?
People had all sort of problems when using Apple unsanctioned Clang binaries (problems when Xcode updates, other software gets confused if you add your new Clang to the system PATH). It is easy to get in trouble, better to avoid the problem.
In theory, yes, you should be able to run a different version of Clang side by side.
I think it's really sad that I often see people on public transport in the UK just offload a device onto their children to placate them when they're bored.
I've found generally it's fine for most things but issues come from when the scientific libraries are built with/without certain options. The lack of OpenMP for FFTW is annoying, for example.
Yes, that's of course a potential issue with any distribution. The good news is that's relatively easy to tweak their recipe to build your own version.