Granted, the emphasis has been on applied mathematics. I think in the longer run it will branch in several directions, one being realtime simulation - and then on to games. It is close to C++ efficiency (plus or minus) already, and it will only get better.
I haven't looked into Julia's GC implementation in detail, but I'm hopeful that with a little effort it's easy to avoid "stop the world" GC collections.
Programming is the art of getting a particular machine to do something you want. You may use math to get there (like in accounting or swimming) but its fundamentally a task that's performed by skilled people.
This week I have used Julia for running SQL against SQLite, manipulating dictionaries, raytracing, statistical analysis, engineering problems, simplex optimization, processing data from Excel, k-means clustering.
I'm pretty sure none of these would be classed as high-level math exactly, though some math is involved.
Any it's not as strongly typed for writing code as you seem to think
function fred(a, b)
return a * b
end
would work to multiply its numeric arguments or concatenate string arguments but it would throw an error on mixed string / numeric argumentsIt also supports duck typing
function jule(a, b)
return a.value * b.value
end
will work no matter the types of a and b so long as they have the required attributesI mean, if Julia works for you, that's great. But it seems a bit awkward to me, and until now (and even now), there was the array indices elephant in the room (it's the Lua problem: Even if you support zero-based arrays, it's not supported by convention).
As a Scheme/Lua/JS/Python/Ruby/C/Whatever else programmer (I don't know them all well, but I like to keep my hand in), I just don't see what Julia gets me. But that's just me.
I've not really found the 1 index much of a problem, makes translating other code a bit awkward.
The new dynamic indexing scheme (0 based, -10 based, whatever) seems interesting.
What Julia gets me is a stats / machine learning environment I had to awkwardly program in Octave.
I don't know, maybe it's great. Maybe I should reconsider. But then again, it's strongly typed, which isn't usually my sort of thing (I'm not working with a team, and my programs haven't devolved into chaos yet, so with no empirical data either way, I'll take my favorite)