2015 was a completely different world for #julialang. I think it's fine to say it wasn't ready for most people! It wasn't ready for me. But 2018 #julialang is quite awesome, and people have really figured out the right designs for using the language to its fullest.
-
-
-
Yes. If I wasn't strapped for time, I'd really do a deep dive again. (And, update my now failing packages!)
End of conversation
New conversation -
-
-
Did any Julia ABM packages pop up since that post? Genuinely interested!
-
I don't follow julia enough to know or make a good recommendation. But, I had some talks with prominent contributors back then about what horizon features that would make expressions ABM easier. So, I'm sure there are!
End of conversation
New conversation -
-
-
I think that the the new package manager in
#JuliaLang v1.0 exactly addresses your concerns about reproducibility, doesn't it? -
I'm not sure because I haven't kept up-to-date. But, I'll signal boost this because a lot of my followers are dedicated julians.
- 1 more reply
New conversation -
-
-
Your impedance mismatch might be really a problem transitioning from single dispatch to Julia’s multiple dispatch. It’s not just about bundling data members into a data object and separating out methods. Your approach to OOP has to change it can be tricky to make that transition
-
You have to further decompose your classes to smaller abstractions and use these blocks to build up your classes. Rather than inheriting and modifying fat objects, you create highly compartmentalised objects related to each other through abstract classes and compositions.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.