Re:Julia 1.6: what has changed since Julia 1.0?
by krastanov on Sunday February 14, 2021 @10:02PM
(#26138590)
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.
Re:Julia 1.6: what has changed since Julia 1.0?
by ecnahc515 on Sunday February 14, 2021 @10:12PM
(#26138646)
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.
Re:Julia 1.6: what has changed since Julia 1.0?
by aliceryhl on Monday February 15, 2021 @03:52AM
(#26140607)
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.
Re:Julia 1.6: what has changed since Julia 1.0?
by gugagore on Sunday February 14, 2021 @09:47PM
(#26138501)
Why do you want `julia-pkg add StaticArrays` when you can do `julia -e 'use Pkg; Pkg.add("StaticArrays")'`, though?
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:
You could do it also like this: There is no `julia-pkg add StaticArrays`, unfortunately.