On Thu, Feb 16, 2017 at 8:44 AM, William Stein <wst...@gmail.com> wrote: > On Wed, Feb 15, 2017 at 11:26 PM, Emmanuel Charpentier > <emanuel.charpent...@gmail.com> wrote: >> Dear list, >>[...] >> The trade-offs are not obvious. No solution dominates the other. But both >> solutions explored here (WSL vs Cygwin) seem to dominate the VM solution. > > Did you try actually using a VM on this computer? My experience with > Windows to date has been that for a technically sophisticated user who > cares about performance (like you), using VirtualBox is vastly > superior to WSL or Cygwin...
Docker is another option here, lighter-weight than using a full VM (granted, Docker for Windows does run a lightweight Linux VM). Since I do so much work on Windows these days I actually do a lot of my Sage work (on Linux) in a Docker container. Performance is on par with running on bare metal since, for the most part, you are. The only problem I have with it right now is that shared directories between the Windows host and the Docker VM, while functional, have problems with symlinks. As of a few months ago symlinks *work*, but it's still buggy. I believe this may actually be due to a bug in cifs on Linux but I haven't investigated deeply yet. In any case, the workaround is to put your source code in a Docker volume, in which case it's actually on an ext4 filesystem inside the Linux VM. Just make sure to give the VM image a decent amount of disk space. This has been the best option for me, as a power user (in conjunction with Cygwin for general shell-based tasks). -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
