Thanks for your response, James. > 1. The newest 0.3 binaries are supposed to contain the sys.dylib file > (it's sys.so on linux, and so I have started to just call it that > everywhere for simplicity) and thereby gain the accelerated startup > time. I'm not sure why this would be failing for you. >
Apparently the Ubuntu nightlies (which are the relevant binaries for me: it seems there is no single file binary tar.gz download or anything like that, only a Windows installer, a Mac OS X .dmg and the Ubuntu PPA repo), don't have it yet but will by tomorrow, according to Elliot Saba. So my problem is solved by ignoring it for a day, that's definitely the best sort of problem to have. 2. You can write a base/userimg.jl file, which will be precompiled > along with the rest of base Julia. Gradual work is being done to > address the startup time for external packages. > Can you explain more about this? What do you mean "will be" precompiled, what do I have to do to make it happen? If I create, say, an empty base/userimg.jl and start Julia will it write out the missing sys.dylib so that on future runs I don't have to wait 20 seconds? If so, why does this depend on the existence of userimg.jl? Why doesn't Julia notice I don't have a sys.dylib and make one for me on the first run? > 3. Julia uses ~/.julia > Well, yes, it does use it. It installs source code of Julia packages there for example. But it doesn't seem to cache results of compilation. Right now, since I don't have this magical sys.dylib, for example, I get 20 second start up times every single time, so it isn't caching the compiled standard library anywhere, right?
