Sukera

Sure! 'C' in the debug REPL enters compiled mode.

https://github.com/JuliaDebug/Debugger.jl#compiled-mode

> My biggest qualm with Julia (and maybe this speaks to my inexperience with the language) is that it isn't always obvious when Julia is going to make a copy.

If you're talking about slices of an array, those always create a copy unless created with the @views macro (or the equivalent function call).

Do you have a source on that? Quite a few people seem to disagree: https://istlsfastyet.com/

> You can see some of the ideas in Julia or LuaJIT, but you pay a penalty on what can be dynamic.

I'm sorry but I think I'm missing something here - what sort of penalty are you paying in terms of dynamicness? Can you be more specific?

- Doesn't compile to native code (there are ways to do it, but too complicated and there are caveats).

What do you mean by that? It absolutely is compiled to e.g. x86_64 instructions by default, going through LLVM. Do you mean no standalone binaries? If so, that's actively being worked on by e.g. PackageCompiler.

https://github.com/JuliaLang/PackageCompiler.jl

Yes, all kinds of jobs - but are there actually a substantial number of people doing those jobs compared to the number of jobs that are easy to automate away?

> Quick note: The situation is not different on Linux, MacOS, or other operating systems because all executable formats have some way to embed images. What publishers should do is remove unncessary metadata before publishing, which is easy to do in the case of the PNG because we can simply omit the iTXt chunk.

From your link - so I guess the situation on linux isn't different? Or am I missing something, other than that it depends on the embedded PNG?