I totally agree that having dynamic dispatch in the first position of the features list, for example, does not help. But, in my opinion, it is ok for a pre-1.0 language. That is what makes exciting seeing some external help to release a stable version.
It can be a very interesting feature for somebody into language design, but the average Joe working in a lab is not going to learn a completely new language and rewrite all his Matlab code because of it. Most probably, he has not idea what it is or why he would want it.
It was an example of how, at this point, it seems like the web site is more directed towards language developers than potential users.
In this regard, multiple dispatch is actually a huge selling point! I've written in Fortran 90 code, C, Python, and enjoyed most of those languages. There is something unique about being able to pull up the source code for almost every operator/function in the language, implemented in that language. Fortran has this, but is much more statically oriented and difficult for quick scripting. Python, well I'm hopeful pypy keeps building momentum. Or perhaps Pyrhon ported to web assembly, in more pure Python.
Apparently Python is having some success there http://blog.mikiobraun.de/2013/11/how-python-became-the-lang...
It seems to be really hard to create smooth user experiences for the common use cases of such complex products. I think people have been trying to oust Matlab for 31 years or so.
Disclaimer: I haven't checked Julia for a few years. Requiring hand reloading of files after editing and no native graph support were a few major problems for a workflow back then.