Kristoffer Carlsson

I think that the interruption has to be disabled until a known safe point if this is supposed to work reliably.

Posting this discussion here: https://discourse.julialang.org/t/julia-bin-as-a-standard-location-for-scripts/45993. Some quick thoughts/ideas. The exact name of stuff are not that important. 1. An application is a Julia project (note, not a package) that comes...

> For example, consider an image editor that runs plugins. A simpler but more concrete example is GameZero, which behaves as an app in that it has a command line...

> >How do you "dev" an app? Just clone it and then you manually run julia bin/foo_1.jl? > I'd say yes, just clone it. I thought about this some more...

> This allows Julia to precompile the command_main(::Vector{String}) function so for simple CLIs we can have almost zero extra start-up time. Yes, I agree that the application needs to support...

> It does not contain any Julia code by itself. > Each application entry point is implemented as a function in a package listed in the Manifest.toml file of the...

> My point is that code is usually reusable. If the entry-point function does not call exit, I think the majority of "CLI" is actually totally usable as a library....

> Since Manifest.toml file can contain URL and relative path, I don't think that's necessary. That's a good point and then the difference between library and application code becomes moot....

> The main point I wanted to emphasize was that having a package-compatible directory structure reduces the things Julia programmers have to learn and also infrastructures such as Pkg.jl have...

> we can consider provide an option to compile the entire application as standalone executable on registry side, and even Julia itself can be one of the application on this...