5 ms·
JuliaCon 2015 Preview
- elliott34 11y agoIs anyone on HN using Julia professionally?
- idunning 11y agoNot sure they are on HN, but I know a few companies at least are using the JuliaOpt[1]/ JuMP[2] stack. [1]: http://juliaopt.org http://juliaopt.org [2]: https://github.com/JuliaOpt/JuMP.jl https://github.com/JuliaOpt/JuMP.jl
- rrock 11y agoYes, I've used it for a number of academic research problems in biophysics. Our first manuscript that used it is in review right now. To get "real work" done, I stuck with the 0.3 line. I've found it to be quite stable. Master is quite lively but should be settling down soon, at which point I'll migrate.
- Argentum01 11y agoI used it professionally from 2012 - 2014, and I know of about a half a dozen companies either developing things in it or supporting it as part of saas offerings. Not that many, but each group that I know of made the switch after extensive reviews of other language options, and they've all had positive experiences so far.
- deleted 11y ago[deleted]
- idunning 11y agoIf anyone has any questions about this post or the conference, fire away! Last year's first conference was a big success in my opinion. Videos are available at http://juliacon.org/2014/ http://juliacon.org/2014/, although the speakers weren't mic'ed so the sound isn't so great - we'll be fixing that this year.
- pbowyer 11y agoThis looks fantastic! Are there any plans for a European conference?
- one-more-minute 11y agoThere's definitely some interest in holding a conference from the community over here – we'll probably have a go at gauging general interest and forming more concrete plans soon.
- merqurio 11y agoThat would be great !
- idunning 11y agoNot definite plans, but serious thought is being given to having it in Europe next year if all the necessary bits can come together.
- vanderZwan 11y ago> although the speakers weren't mic'ed so the sound isn't so great - we'll be fixing that this year. That's great, it was the only significant annoyance last time! Looking forward to see what people have been doing with this language last year.
- transfire 11y agoIs anyone talking about the future of the module system?
- idunning 11y agoNo, I don't think so. I don't think there is much that is going to change with modules in the future, or at least I'm unaware of any open issues about it. What did you have in mind? The hackathon on Wednesday will be a particularly good time to bounce around your ideas, and is free to attend.
- transfire 11y agoBecause the current system (http://julia.readthedocs.org/en/latest/manual/modules/ http://julia.readthedocs.org/en/latest/manual/modules/) is just sad. It's the one thing that has kept me from fully embracing Julia. I would love to go if I were any where in the neighborhood. But alas I'm over a thousand miles away.
- idunning 11y agoOuch, "just sad"... would be interested to hear more! Even if you can't attend, anything you could write up as either a blog post, a Github issue, anything, would be helpful for getting some discussions going around it at the conference I'm sure.
- sgt101 11y agoSome people I've talked to have complained that modules aren't objects, and that throwing away the coupling of types and reuse files is "abandoning 30 years of learning" and that "I don't trust myself to be disciplined" I think that these arguments are not strong! But what would be useful would be some detailed critical thinking on the topic. My take is that thinking about where you put multiple dispatch parameterized type matched code components is actually a real challenge. The module structure chosen for a library requires "artful" approaches. Perhaps a good workshop on the topic would yield a guide or an approach to making these decisions? Perhaps a labeling system could be evolved to provide metadata for modules better enabling reuse and promoting discover-ability ? Perhaps static analysis of a code base might be provided that gives recommendations (and assistance) for creating good decompositions and associations?