381–390 of 423 posts
Earlier quoted context omitted.
Did MSFT start giving commit/moderation rights to outsiders on their repos? I assumed only MSFT org members can add tags to issues etc.
Apparently. The comment box is enabled for me for example.
I will need to monitor this more closely. I have switched to a WIN/WSL2 setup recently from Mac and have not had this problem happen to me. Nonetheless I hope this gets fixed before it hits me.
Keep the Mac handy. I just went the other way to you because of a thousand paper cuts.
Combine this with Endpoint Management crapware from my employer and you have a toxic combination. Esp. as said crapware is primarily targeted and optimized for WIN machines as the parent company is > 500k WIN machines and only about 25k - 40k Mac machines.
Sad, as I really loved the pre 2018 MB Pros and it was a blast doing my data analysis work there.
Earlier quoted context omitted.
What is it about Windows that makes this a problem where macOS and Linux seem to be fine? The same mechanisms exist in all three major operating systems, which is to say that technically any executable I choose to run on my computer can load a file and interpret it. Is it really just that Windows users download and run random junk? It's been so long that I've seen a virus of any kind anywhere at all that I genuinely…
It's possible you don't see random toolbars and malware now because Defender works. Microsoft could be smarter and offer default exclusions for some things.
Earlier quoted context omitted.
Why would VM-based WSL2 use any less RAM?
WSL VMs are gen2 (fully paravirtual) hyper-v VMs, so use dynamic memory allocation. VirtualBox, even with Hyper-V as its engine, doesn't do this. I don't think any standalone Linux distros offer a standalone Hyper-V paravirtual image that is not a WSL2 image.
Earlier quoted context omitted.
It's not enabled by default. Enabling Hyper-V still causes a battery/performance hit that is going to be hard to get rid of.
Virtualization-based security -- a lighter mode of Hyper-V sans real VMs -- is enabled by default on new installs on recent-enough hardware: https://techcommunity.microsoft.com/t5/virtualization/virtua...
Earlier quoted context omitted.
Also opposite anecdote, I switched from Pop!_OS to Windows after getting into music production recently as a hobby (MIDI controller driver software doesn't always play well, even with WINE-devel) after over a decade on Linux. I expected to hate it, but I'm asking myself why I didn't do this sooner. It's the same sort of scenario as before -- I have Windows running the games I occasionally play, and music stuff, and I…
I've recently come across the same issue with DAWs. Settled on having multiple machines and switching the drives if I need to reuse a workstation for something else. Most of the time you can dedicate cheap systems to specific utilizations, it will save you time and effort. e.g. There is no reason for your DAW machine to also be your gaming machine as the hardware requirements are pretty different.
While we're on the topic of WSL2 causing issues, I will add one that I noted to the pile. If you have WSL2 installed then the first bash on PATH is the WSL2 version of bash. For whatever reason, this version of bash has a major impedance mismatch with Emacs and org-mode. From windows native Emacs (not an Emacs installed in WSL2) if you try to run an org babel block that contains bash code, whole commands will simply…
Earlier quoted context omitted.
Virtualization-based security -- a lighter mode of Hyper-V sans real VMs -- is enabled by default on new installs on recent-enough hardware: https://techcommunity.microsoft.com/t5/virtualization/virtua...
The link you posted only contains one device and it happens to be an ARM device. Seeing the impact it still has on battery life at least on x86, I really doubt they have enabled it by default. It was not enabled by default on x86 in 2020 at least.
If you click through "capable hardware" to here[1], you'll see the list of requirements for VBS, including:
> Virtualization-based security (VBS) requires the Windows hypervisor, which is only supported on 64-bit IA processors with virtualization extensions, including Intel VT-X and AMD-v.
So it will never be the case on x86/IA32
1: https://docs.microsoft.com/en-us/windows-hardware/design/dev...
Earlier quoted context omitted.
> That's a minor incovenience at worst. What a bizarre claim. It's irrelevant if you don't need Postgres, a minor inconvenience if you can easily adopt a workaround, and a show stopper if you were relying on accessing a local Postgres instance.
Can't you just run Postgres natively on Windows? It's a database, you can talk to it from WSL over a local socket, no?
Earlier quoted context omitted.
WSL2 uses hyper-v. You can only run either hyper-v or ESXi (VB's hypervisor) at the same time.
That's not longer true. Yes, WSL2 is type-1 hypervisor (which means Linux under WSL2 and windows are both VMs of sort, managed by higher level invisible "main" OS) and initially this made running VMs inside windows impossible (since technically that would be VM inside VM). But this has been fixed for months now - originally not only it was not possible to run virtualbox (or vmware, ESXi is vmware type-1 btw, dont mis…