![]() ![]() ![]() You don’t need containers for perfect reproducibility. The way Julia’s package manager works, when you have a Julia project, it gets its own project environment and the manifest file records the exact Julia version (as of Julia 1.7) and the exact version - down to the last bit - of every package dependency (since Julia 1.0) and every binary dependency (since Julia 1.3).It is very good to know that Julia will live with the decisions made in the past (even if they are suboptimal), and only produce breaking changes if they bring improvements impossible to obtain by just adding things to 1.X. I certainly would not understand making a sed -e "s/angle/arg/g" for trivialities. If you do not like angle(z), or even if we all agree that is an unfortunate name, I would be very happy if it is just deprecated, but that it keeps working. These are the discussions that I do not really understand. Sometimes I read long discusions like this ( ) and I get really worried. And good to know that these are the intentions. In short, the vast majority of Julia 1 code will keep working in Julia 2. I wrote more about the kinds of changes that are of interest here. I’ll say it again: we are not interesting in making gratuitous annoying changes in Julia 2.0. Especially given that we’ve said the opposite many times: the way Julia code looks and feels is done. While Julia 2.0 will by definition be somewhat breaking (or it would just be 1.x for some value of x), it seems like FUD to suppose that a release that hasn’t yet been made will change everything and break everyone’s code.FreeBSD even allows you to get them from the package manager. I have several versions of gfortran installed (no containers). ¿What happens with your binaries if we move away from amd64? The statement of different compiler version is just wrong. The upshot is that if you need an old Julia version for whatever reason, you can easily install and use an old version just for one specific project. This is notably not the case for most C, C++ or Fortran compilers, which like to assume they own the entire system - if you want to use more than one version of gfortran at the same time, you’re going to need containers. As noted, they’re easy to install and use alongside each other. We keep binaries for every Julia release.And Honestly, I will be more happy if Julia would never move to 2.X. We test every registered package in the entire open source ecosystem with every release to make sure we haven’t accidentally broken anything. We take not making breaking changes in 1.x releases of Julia very seriously.Without entering in a useless discussion, I want to clarify some things: I agree that Julia takes compatibility and reproducibility very seriously, but I think that it is honest to say that Fortran also does it, and to a degree not seen before or after. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |