It's a shame you can't just turn on live TRIM support.
This kind of disk image is a bunch of multi-megabyte blocks of data, plus a list of where each block goes on the virtual disk. Implementations can support TRIM by deleting the block that's zeroed and moving the block at the end of the file into that spot. VirtualBox can do this, shrinking the file when the guest OS TRIMs, but Hyper-V can't.
It'd be very strange if there is not.
Nope, they don't eat up space. One of the fun side effects of sparse files on NTFS is calling WriteFile on the sparse file can lead to an ERROR_DISK_QUOTA_EXCEEDED error, which applications tend to not expect.
If sparse files didn't save on actual space allocations, it would simply be a lie to call them sparse files. Granted, that's totally something Microsoft would do, and has done for other features they lack, but that doesn't seem to be the case here.
I thought I didn't know about "Throw-And-Exit" command, but no, my powershell doesn't have that and google also doesn't know a thing, so wonder what's up with that.
And instead of manual confirmations, one can write script with ShouldProcess support to have support for builtin -Confirm/-WhatIf/-Force parameters. And it would actually be a great use case for that scheduled task to run with -Force parameter instead of changing code to strip out confirmations. https://learn.microsoft.com/en-us/powershell/scripting/learn...
> The throw keyword causes a terminating error. You can use the throw keyword to stop the processing of a command, function, or script.
Looking at the source, it seems to use a `wsl --export` option rather than `diskpart`.
I used to think a windows laptop would be better for hardware management, maybe it is but I just gave up and installed Linux. My life is so much easier.
My biggest frustration with WSL at present is that 1Password won’t properly support proxying their ssh agent into it. (Though in googling it again just now, I see a suggestion to try something called npiperelay, so I’ll spend some time seeing again if I can get that working)
If you happen to use Nix, I have a quick and easy package at github:Cu3PO42/gleaming-glacier/next#wsl-ssh-agent. Simply install that and 'source $(which wsl-ssh-agent)' in your bashrc and you should be good to go. (There's also a HM module in the Flake.)
Like even if you prefer Linux, Mac is a huge step up over windows and WSL if those were your only options.
Also latest Mac machines aren't even that overpriced as they were before their in-house CPUs, for the performance you get really there is only one PC chip out there right now that can be compared and that chip is available in like 2 laptops.
Linux is Linux Windows offers Wsl1 and Wsl2 integration
The closest thing macOS has in any official capacity is their containers project, running each container in a VM for "security" at the expense of poor resource allocation and no compatibility with table stakes tooling like compose.
However, in practice, at least for the kind of compiling I do, AWS EC2 VMs tend not to be faster than my cheap HP Elitebook. Maybe if you can leverage a hefty number of cores, the situation is different. For regular email pushing, the laptop is good enough.
The more I work with secops people the more I fail to trust or respect them.
It's pretty miserable in terms of latency and window management. If you can get this to work well with NX or X forwarding, that's cool, but it's a second class offering when that's your only option.
My home internet connection pretty low latency (wired) and pretty high throughput (gigabit).
It's not absolute torture using the AVD, but it's definitely clunky.
I watched a colleague use VSCode earlier today and was kinda shocked at the amount of pop-ups, and also how they'd cover the active pane, including what the developer was typing.
My attention system isn't built for modern Microsoft apps, I think.
Now if i want linux, WSL2, and if i want linux graphic, Vmware or something similar
My experience is the exact opposite. When I let my laptop running windows sleep overnight, in the morning it's warm. Under Linux, it's room-temperature. I rarely run Windows on it, so there's no checking for mail or whatever in the background, I only have 2-3 games, Prime Video and Lightroom installed. It's also kept up to date, so no updates to install.
But, at least it now wakes back up. Up until a few months ago, it would randomly freeze up or die and reboot and get stuck at the Linux ZFS decryption prompt (I dual boot, and Linux is first). This is a 2020 model laptop, which didn't work under a fresh Windows install out of the box. The webcam wasn't working for a good 3 years (apparently some USB chip wasn't detected). The only issue I have under Linux is that the mic mute LED sometimes turns off even though the mic is muted. It's a standard-fare HP Enterprise, no dual GPU or anything fancy.
Of course, I can't understand why Microsoft or Linux distribution contributors along with software vendors never manage to truly "fix" such important usability issues.
I was pleasantly surprised when I bought a Mac (M1 MBP) a few years ago. It doesn't have all the idiot behaviours that Windows and Linux seems to have. It's so boring. It just works. If the Linux/Windows folk can nail that quality down it'd be nice but I have my doubts it'll ever happen (after trying for about 30 years!)
They won't let me have a Linux box because I'm supposed to be a windows desktop dev (now about 10% of my workload) and they don't like Linux because none of the invasive security and VPN crap they add works on it.
I use a Mac at home. Mostly proper Unix at your fingertips. Feels much less dirty than either solution.