4 ms·
When I last looked at Julia, the language wasn't yet stable. It's not fun developing packages for a language that changes from release to release, so I don't ex
by freyir 9y ago
When I last looked at Julia, the language wasn't yet stable. It's not fun developing packages for a language that changes from release to release, so I don't expect their ecosystem to stand a chance until they get to v1.0. All the advantages for package developers listed in this article are moot while the language remains a moving target.
It was said that v1.0 was due in early/mid 2017, but it looks like it's still a ways off.
There is (or was) a window of opportunity for Julia to steal mindshare in academia from MATLAB and R, but it feels like Python is beating them to the punch. Of course, Python had a 21 year head start.
- kgwgk 9y agoI was going to add that Python has been "getting there" since 1995, but I see you have already edited you comment :-)
- sgt101 9y agoTalking to people in the community my impression was that 1.0 would appear when 1.0 appeared and that they felt that given the difficulties faced by other languages and the work required to produce a language that was fit for purpose in the modern context, a gestation time of more than a couple of years was reasonable. In terms of community I think that the economics community and private equity firms in particular seem to have picked Julia up enthusiastically. Having said that, I suspect that it will be three years before Julia becomes mainstream, and then it will be a minority choice for five or six more - if it is the big success it deserves to be!