3 ms·
Having migrated my Python+Fortran code to Julia in October last year I would say yes. For reasons why I would read the documentation basics, check the benchmark
by montalbano 8y ago
Having migrated my Python+Fortran code to Julia in October last year I would say yes. For reasons why I would read the documentation basics, check the benchmarks and play with a bit of code. I was sceptical when my advisor originally suggested it but now I dread the thought of scientific software in any other language.
- nerdponx 8y agoIMO industry will start switching once a Scikit-learn or Caret equivalent for Julia shows up. PyCall.jl and RCall.jl should take care of everything else until the rest of the ecosystem catches up.
- FridgeSeal 8y agoLast time I tried to move all my stuff to Julia I ran into issues with the data frame equivalent package. It seemed the devs and community were in debate as to whether Julia and the dataframe should be more pure numerical focused a la matlab or python/pandas and appropriate for data analysis. As such null values were handled weird or not supported, which made it practically useless for all of my use cases. I’d love to know if that was still the case though, because I’d so much rather use Julia than Python for my analysis and stuff.
- Certhas 8y agoActually 0.7 made a big step in resolving these issues: https://julialang.org/blog/2018/06/missing https://julialang.org/blog/2018/06/missing
- FridgeSeal 8y agoLike music to my ears!
- montalbano 8y agoNot necessarily, I recommend the talk given today at JuliaCon by the head of an actuary research group at Aviva - a very large insurance company: https://www.youtube.com/watch?v=_jx1VmWxgVY https://www.youtube.com/watch?v=_jx1VmWxgVY They've been using it sucessfully for quite some time.