4 ms·

Julia does support REPL style development, and the little I have used it, it was effective for deep learning, text processing, and SPARQL/linked data clients.

Sanguinaire 5y ago
I would say that Julia not only supports a REPL, but is heavily biased towards its usage - enough to be detrimental IMO.
- vindarel 5y ago
  but its REPL is slow and not as interactive.
- hpcjoe 5y ago
  My biggest complaint is static compilation. There are things you can do with PackageCompiler, but they don't work for some of the code I write. This makes deployment of artefacts harder than it needs to be. Most of the infrastructure is there in the code, it just needs to be tied together, in such a way that juliac file.jl -o file.x results in a deployable (preferably static) binary.
- the__alchemist 5y ago
  To clarify (Correct me if this isn't what you mean), Julia compiles not only program code, but dependency code each time you run a program. This can make simple programs and scripts take a long time to start. A common response is "Use the REPL", where it compiles the dependencies once at load.
  - borodi 5y ago
    Julia has a JIT compiler but it doesn't store the compiled code between sessions. This can add a delay on the first time you call a function. By keeping the REPL open you can avoid having these delays multiple times.
hpcjoe 5y ago
I've been writing "scripts" with it that extract multi GB data sets using various APIs, perform relevant processing, and spit out actionable visualizations and data. The APIs are (these days) mostly web/REST-ish, though I'm starting to work on writing some wire-protocol stuff as well. It (Julia) is an amazingly powerful language today. Excellent for data scientists and engineers, for deep and complex analytics. I am using it in a professional (e.g. paid) setting. Along side python, C++, and other things.

Sanguinaire 5y ago

I would say that Julia not only supports a REPL, but is heavily biased towards its usage - enough to be detrimental IMO.

vindarel 5y ago
but its REPL is slow and not as interactive.
hpcjoe 5y ago
My biggest complaint is static compilation. There are things you can do with PackageCompiler, but they don't work for some of the code I write. This makes deployment of artefacts harder than it needs to be. Most of the infrastructure is there in the code, it just needs to be tied together, in such a way that juliac file.jl -o file.x results in a deployable (preferably static) binary.
the__alchemist 5y ago
To clarify (Correct me if this isn't what you mean), Julia compiles not only program code, but dependency code each time you run a program. This can make simple programs and scripts take a long time to start. A common response is "Use the REPL", where it compiles the dependencies once at load.
- borodi 5y ago
  Julia has a JIT compiler but it doesn't store the compiled code between sessions. This can add a delay on the first time you call a function. By keeping the REPL open you can avoid having these delays multiple times.

hpcjoe 5y ago

I've been writing "scripts" with it that extract multi GB data sets using various APIs, perform relevant processing, and spit out actionable visualizations and data. The APIs are (these days) mostly web/REST-ish, though I'm starting to work on writing some wire-protocol stuff as well. It (Julia) is an amazingly powerful language today. Excellent for data scientists and engineers, for deep and complex analytics. I am using it in a professional (e.g. paid) setting. Along side python, C++, and other things.