6 ms·

I'm assuming you may not be familiar with Julia, but basically every "tool" you use in Julia is a library. It requires importing it in the Julia REPL or activa

I'm assuming you may not be familiar with Julia, but basically every "tool" you use in Julia is a library. It requires importing it in the Julia REPL or activating a new contextual REPL within the Julia REPL. You can then start calling the functions from the imported module. You don't really get standalone Julia tools, it's all libraries and you're always starting the REPL, importing something, then doing stuff from inside the REPL. For example, installing a package in Julia is the following steps: julia ] # keybinding which activates pkg mode add StaticArrays You could do it also like this: julia -e 'use Pkg; Pkg.add("StaticArrays")' There is no `julia-pkg add StaticArrays`, unfortunately.

gugagore 6y ago
Why do you want `julia-pkg add StaticArrays` when you can do `julia -e 'use Pkg; Pkg.add("StaticArrays")'`, though?
- detaro 6y ago
  it looks a lot more annoying to type. Would be an easy shell alias or script though, if one prefers that command style.
- ecnahc515 6y ago
  I don't use Julia regularly, it's just an example of making it clear how the REPL is core to using Julia.
krastanov 6y ago
I am pretty incredulous at this counting as "forcing you to use a REPL". It is a couple of extra characters compared to what pip, nvm, cargo do, and you can just make your own shell alias for it. And I am not even mentioning the significant advantages it has over pip, especially for binary dependencies.
- ecnahc515 6y ago
  Shell aliases aren't as useful in a CI pipeline, or when trying to provide instructions on how new to Julia installs a new package. Also, with Julia being so different from everything else does mean everyone has to learn a new way of doing things. This isn't a bad thing, I like that Julia has a programmatic API for most of these things, but the UX is definitely not amazing.
aliceryhl 6y ago
This is not a problem for me. I can write a `.jl` file and call it from the command-line with imports in that file. The problem is compile-times, since every run is first run when running a script.

gugagore 6y ago

Why do you want `julia-pkg add StaticArrays` when you can do `julia -e 'use Pkg; Pkg.add("StaticArrays")'`, though?

detaro 6y ago
it looks a lot more annoying to type. Would be an easy shell alias or script though, if one prefers that command style.
ecnahc515 6y ago
I don't use Julia regularly, it's just an example of making it clear how the REPL is core to using Julia.

krastanov 6y ago

I am pretty incredulous at this counting as "forcing you to use a REPL". It is a couple of extra characters compared to what pip, nvm, cargo do, and you can just make your own shell alias for it. And I am not even mentioning the significant advantages it has over pip, especially for binary dependencies.

ecnahc515 6y ago
Shell aliases aren't as useful in a CI pipeline, or when trying to provide instructions on how new to Julia installs a new package. Also, with Julia being so different from everything else does mean everyone has to learn a new way of doing things. This isn't a bad thing, I like that Julia has a programmatic API for most of these things, but the UX is definitely not amazing.

aliceryhl 6y ago

This is not a problem for me. I can write a `.jl` file and call it from the command-line with imports in that file. The problem is compile-times, since every run is first run when running a script.