Here are a few more improvements in v1.7 off the top of my head:
* Further latency improvements (though much smaller than for 1.6)
* Big gains in inference precision for the compiler
* The above also unlocks better static analysis
* Improved speed for the package manager on Windows
* Begin work on adding atomics
* Thread-safe RNG
I'm sure there is more I've missed - I don't hack on Base Julia much.
However, I think it is unfair to compare the inclusion of log10 to the work required to get solutions to these harder problems. I guess why not both? ;)
Julia 1.6 (LLVM 11) and Julia 1.7 (LLVM 12) use the LLVM versions that were current, when the release branch was cut. LLVM 13 was finalized a fes days ago and will be released this week.
So I am not sure where the notion comes from that Julia is lagging behind.
There are? I mean, with every new LLVM release a few things gets faster and a few things slower but I am not aware of any big changes in the recent LLVM releases. Do you have any more information about that?
Our use case involves dynamically displaying some analysis results on a status page derived from data from the field. The analysis was originally written in Python + scipy + matplotlib (Julia in OP's case). Why write the analysis code a second time just to display it on a demand-generated webpage?
You don't have to run the entire website on Julia, but maybe you do want to stand up a couple of RESTful endpoints that are integrated with the rest of the web application. If Julia can't do that, then your options will be limited.
Faster log10 is all nice but I would love to see a more aggressive compilation cache and improved tooling rather than these minor improvements.