On Mon, Dec 16, 2019 at 4:39 PM Emmanuel Charpentier <emanuel.charpent...@gmail.com> wrote: > Le lundi 16 décembre 2019 16:13:09 UTC+1, E. Madison Bray a écrit : > > [ Bandwidth savings... ] > >> > What I mean is that a Windows program can't call a Cygwin program >> > "transparently" and, vice-versa, a Cygwin program can't transparently call >> > a Windows program. Some common operatins (redirection/piping) are awkward >> > (if ever possible). >> >> It works in many cases but some cases do require finesse. > > > That's the problem... > >> >> I don't >> think that has anything to do with whether not Sage itself is a "first >> class citizen". > > > Again, my choice of words may hjave been suboptimal... > > >> >> The only extent to which it isn't is that >> >> there still is not a stable buildbot for Windows, despite my efforts, >> >> as it tends to need more maintenance than a Linux server would... very >> >> annoying. Other than that I don't know what you mean. So I don't >> >> think you should be giving anyone the wrong impressions here. >> > >> > >> > I should have been clearer (i tried in the lines above...). >> >> Yeah, this makes sense. It would still be ideal if Sage could run >> 100% natively on Windows, but that's an effort that will require I >> think at least another 3 years of funding for one full-time employee >> =) > > > I've heard pleasant things about WSL2, which *might* become an alternate > solution (if and when it is released for public consumption, not for > "Insider" use...). It boasts "two-way transparency" in those inter-system > calls. > > It's Windows 10-only, but Windows 7 is due for end of support in January > 2020, and windows 8 is already (as far I understand Microsoft policies) in > "extended support" (i. e. not very much maintained beyond obvious security > issues).
Same thing I've always said about WSL: It's fine for power users and developers, but is not available by default nor designed for end-user software installation. WSL 2 is even somewhat worse in this regard: With WSL 1 they were trying to build POSIX-compatibility directly into the kernel, so hypothetically it would be possible one day to install software containing ELF binaries on Windows and have it "just work" (even if that was not made to work by design initially). Now they've given up on that (surprise surprise, it's hard! Maybe they should have hired some of the Cygwin devs...), and WSL 2 just runs custom-built Linux kernel in a VM using Hyper-V, meaning for WSL 2 to work users must install Hyper-V and enable hardware virtualization in their BIOS. Again, fine for power-users--completely inaccessible for people who just want to install Sage. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAOTD34ZG9i3gJ%2B_BBvGnck5eN6LZhtoMj-6pYS9tdgN0nSAGQg%40mail.gmail.com.
