3 ms·
Lots of truths there but also colored by someone who evidently has not been a fan of technologies before and seen how it works. I am not as pessimistic as a Ju
by socialdemocrat 6y ago
Lots of truths there but also colored by someone who evidently has not been a fan of technologies before and seen how it works.
I am not as pessimistic as a Julia fan. Why? Because I have been where this guy is now ever since I was an Amiga user. I was like that with Python, Ruby, Go and a whole other languages.
And what I learned from that is that it takes time. Neither Python, Ruby or Go had success over night. Yet almost all these languages I homed in on in the past have seen what I would call success later.
I was certain Perl would go downhill when it was at its top. I kept argue with Perl fans that Python was a cleaner language that would see more success. Ditto with Ruby. That turned out to be quite accurate.
I said while D looked like a nice replacement for C++, it simply wasn't big enough improvement to go anywhere. That also seems to have been an accurate prediction.
Go on the other hand had a very obvious appeal from the get go. It did something important different and sufficiently better than before while keeping things simple.
I am confident about Julia, because I have not in 20 years since a language with so much potential and so many advantages. You just got to give it time. This reminds me of myself following solar and wind energy in the early 90s and deciding it was not going anywhere.
Ironically I see people like Michael Shellenberger having become a cynic about wind and solar now that it has actually achieved some measure of success. Why? Because it didn't happen fast enough. He poured all his enthusiasm and hope into this industry long before there was reasons to do so.
People have to be aware of the same about Julia. It is not taking over the world any time soon. There is a long road ahead. And I would not define success as getting to Python scale. But if Julia can get to a similar position as Go is today, then I would call that success.
- zhdc1 6y agoJulia's already making (fairly substantial) in roads. It's just not as visible as Python, since the niche it's occupying is much smaller and out of the way.
- hatmatrix 6y agoWhen Julia finally comes of age, there will be a new, emerging language claiming it will eat Julia for lunch.
- socialdemocrat 6y agoAbsolutely and there is nothing wrong with that. But over the decades I have followed computing I have seen languages with much smaller advantage relative to the competition than Julia rise to prominence. But I am also pretty sure that whatever replaces Julia in the future, it will have borrowed heavily from Julia in terms of semantics, syntax, libraries etc. Multiple-dispatch that Julia pioneered is almost certainly going to dominate future languages. This is in similar ways to have functional programming has entered almost every mainstream language and OOP entered almost every language before that.
- tempodox 6y agoAFAIK, it was Lisp that pioneered multiple dispatch. It hasn't “dominated” a substantial number of languages since then. Maybe the problems it solves haven't been seen as important enough? I really don't know, it seems such a logical extension of the single dispatch known from many OOP languages.
- cygx 6y agoAFAIK, it was Lisp that pioneered multiple dispatch Cf. CommonLoops, https://en.wikipedia.org/wiki/CommonLoops https://en.wikipedia.org/wiki/CommonLoops
- cbkeller 6y agoArguably it may also be because without JAOT compilation as in Julia, multiple dispatch normally comes with a significant runtime performance cost, as far as I understand.
- lispm 6y agoLanguages have addressed that in a variety of ways before Julia.
- eigenspace 6y ago
- gbrown 6y agoI rewrote some stochastic simulation R code in Julia recently, and it sure feels like the future.