My experience is quite different. Although after some hassles I was able to get license but it’s online only.
Overall I’m trying to move away from commercial software (I don’t teach any, only use foss) but yeah Mathematica, MKL + ifort are unbeatable in some respects (Matlab is slowly going to be replaced except some specialised toolboxes, don’t use ansys)
Anyway, proprietary and closed source software is in my opinion harmful for academia. Sometimes a lot, sometimes a little but in general it’s no good, although I understand that it funds some development that wouldn’t be done otherwise.
The typical differences between stuff using ifort/MKL and gfortran/OpenBLAS/BLIS are at least similar, and probably smaller, than the sorts of variation you see anyhow on HPC systems, even without the important large-scale optimizations.
but its far cheaper (and has less bugs) that paying some one to write your own.
Same reason that writing your own crypto is a bad idea.
You don't get the large scale parallel libraries from NAG anyway.
We all know what the quality of academic code reputation is.
do 'we'?
considering a huge amount of common numerical software (esp with any kind of fortran lineage whatsoever) is based in some way on netlib.org code that itself was heavily developed in the BSD UNIX on Vax+ARPANET era within the academic/research community, I'm not really sure that, based on this comment, 'we' do..
The performance advantages are largely mythical too. The last time I ran the Polyhedron benchmarks with beta versions of ifort and gfortran on SKX with the best obvious overall optimization (profile-directed), the bottom line was insignificantly faster with gfortran. Gfortran is infinitely faster on ARM and POWER too.
I wish research councils would support the free software.
Intel Fortran was far superior in language support and binary performance in the mid 2000's and a researcher couldn't be without it.
I don't remember figures and dates, but g77's performance was at least reasonably competitive with proprietary Unix compilers once GCC's backend was sorted out for the architecture (scheduling in particular). It was also mostly more correct. Observationally, researchers could do without ifort, especially on non-x86 hardware -- although ifort morphed from the DEC^WCompaq compiler which was used on our Alphas. (A good deal of work was done for g77 specifically because of problems at the time with portability and availability of compilers for a high profile computational project.)