61–70 of 90 posts
Earlier quoted context omitted.
How did you test it?
Just using a CPU intensive application I work on (GAP, a computer algebra system), on my laptop. I'm hoping we can kill our current windows build, and require people install bash for windows.
Earlier quoted context omitted.
To play older Windows games that for various reasons won't run on Windows 10, for example.
The conventional wisdom has always been that Microsoft is hyper-focused on backwards compatibility, but there's only limited truth in that. Even if you pick Windows XP as a starting point (just considering NT kernels), tons of stuff broke with Vista. Compatibility Mode has never been very good, though I don't think there's anything preventing Microsoft from making a more Wine-like compatibility layer if they really w…
https://www.microsoft.com/en-us/download/details.aspx?id=800...
I'm not sure if the same thing is still available for Windows 10.
Earlier quoted context omitted.
In my experience it's quite the opposite for some workloads: Linux FS and process spawning speeds are typically way faster than Windows one (with or without WSL), so much that even when in a VM with dozen of % of overhead, it is still faster than running on Windows for some workloads (just cold open a random man page under WSL, compared to a VM, and you will understand how much Windows lag behind Linux in some areas…
> just cold open a random man page under WSL, compared to a VM, and you will understand how much Windows lag behind Linux in some areas -- next you can try to build a big program: same result: Windows is really slow) Mate, the thing isn't even released yet and you're bashing it (excuse the pun) for taking too long to open up a man page? Give me a break. After it's actually released and the performance gets better the…
I think Win10 is quite good, and that WSL is quite good given its age, and will be extremely useful for a lot of things.
Still, if you try some workloads, WSL is way slower than a Linux VM. I don't expect it to change for the release. I don't even expect it to change for the 2 years to come. Sill, of course, I could be wrong.
But even so; I insist: WSL is actually quite impressive.
Looks nice.Now give me a good Filesystem à la ZFS and maybe I might come back.
Earlier quoted context omitted.
Just using a CPU intensive application I work on (GAP, a computer algebra system), on my laptop. I'm hoping we can kill our current windows build, and require people install bash for windows.
Is that application in python and uses numpy?
Earlier quoted context omitted.
The conventional wisdom has always been that Microsoft is hyper-focused on backwards compatibility, but there's only limited truth in that. Even if you pick Windows XP as a starting point (just considering NT kernels), tons of stuff broke with Vista. Compatibility Mode has never been very good, though I don't think there's anything preventing Microsoft from making a more Wine-like compatibility layer if they really w…
Microsoft provides a free Windows XP SP3 virtual machine image to run on Windows 7: https://www.microsoft.com/en-us/download/details.aspx?id=800... I'm not sure if the same thing is still available for Windows 10.
Honestly MS is not that good on backward compat. They are good on the story, so/so on the facts. But I prefer that to being stuck in the dark ages of poor design and the poor security which comes with.
I wonder how Microsoft managed to implement the Linux ABI all of sudden, while Wine has been developed for more than 20 years and yet it's still very hard to run most modern Windows software using it. Note this isn't a rant by any way, I appreciate the work done by the Wine project a lot and use it every now and then. I'm just trying to understand if it's a matter of manpower, simpler task, or better design.
The Linux syscall ABI is pretty small and stable, and once you have that any userland program just works. Windows (NT) doesn't have a stable syscall ABI, instead having stable ABIs for libraries that wrap it in various ways (Win32, most prominently, but historically also a POSIX library). As such, WINE has to reimplement all those libraries, whereas Windows only has to implement something comparatively tiny. I expect…