I think getting a usable web stack on julia will take it a long way in terms of making it useful for problems at-scale.
My major nitpick with julia so far, if I can be real, is that its package tooling isn't enough like npm. <_< While this gives away my obvious biases, I do think that spending time on making a really good package ecosystem is important, and is something not enough people take seriously.
It's easy for non-ops people to install packages, but I'm not sure it is easy to do large scale deployments. I'm not hating on npm, but there is still a lot to do with managing all of the dependencies in a way that makes it easy to deploy consistent packages. Pip doesn't solve this problem either, so it isn't unique to npm.
There are some tools for using npm for large scale deployments. Packages are scoped locally to an app, you can bundle them if you want, and there's a "shrinkwrap" command for making sure the installed deps are exactly the same every time. Personally, I would either go with, "peg every version to an exact semver" or "bundle ALL the deps".
My major nitpick with julia so far, if I can be real, is that its package tooling isn't enough like npm. <_< While this gives away my obvious biases, I do think that spending time on making a really good package ecosystem is important, and is something not enough people take seriously.