Re:Julia by Example
by StefanKarpinski on Thursday December 25, 2014 @11:07AM
(#8796485)
For what it's worth, when building from source, the first time compile is the only one that takes an hour. After that, incremental updates are pretty quick since the only thing that usually changes is Julia itself, not the bucket load of source dependencies (LLVM, OpenBLAS, FFTW, GMP, etc.). Most devs pull rebuild Julia from source several times daily – this is the best way to stay bleeding edge (if that's what one wants). Even if one doesn't want to live on the bleeding edge, checking out the release-0.3 branch and building that from source is also an option. That said, the binaries are also a good way to get Julia.
Re:Julia by Example
by kartikkumar on Thursday December 25, 2014 @04:57AM
(#8795934)
Good tip! I've had a number of issues with the Homebrew tap. I've yet to dive in head first. I've been playing around with Juno [1] and like it a lot so far.
I hope we'll see more advanced tutorials appear for Julia soon. I'm quite comfortable with using C++ now for all my scientific computing code, but it really isn't "nice" to work with. It would be nice if there was something like SciPy [2] for Julia, to get researchers going quickly.
Oh, and one more tip for OSX users wanting to try out Julia. You might want to just use the app bundle provided on the Julia homepage rather than compiling from the homebrew tap. I spent close to an hour waiting for all the dependencies to compile before giving up when I realized I don't want to be doing this every time it's updated.