This is not a surprise for anyone that has been using Windows under Parallels on an M1 Mac. What's important is for the real experience to be match the benchmark and it seems to fly for core office/productivity tasks.
I setup a VM for work stuff that includes a bunch of admin policies and work-installed junk a few weeks ago to work while traveling. It didn't even break a sweat and Teams felt as responsive as my recent i7 desktop. At the same time I was able to run all my usual dev stuff on the Mac. It felt like it would handle classic Visual Studio as well, but I didn't want to bother with the install.
Ehh... the answer is it kind of works well, but it really depends on what you're doing since you're running an x64 application (Visual Studio) on an ARM version of Windows running on a Mac M1 in parallels.
.NET development and in particular stepping through debugging is particularly slow, though I guess we should be happy it works at all.
And Arm64 version of .NET Framework (4.8.1). .NET Framework is considered legacy and 4.8 was supposed to be the final version. Not sure whether it means they foresee faster Windows-on-ARM adoption. Or slower .NET Framework to .NET Core transition. Or both.
I setup a VM for work stuff that includes a bunch of admin policies and work-installed junk a few weeks ago to work while traveling. It didn't even break a sweat and Teams felt as responsive as my recent i7 desktop. At the same time I was able to run all my usual dev stuff on the Mac. It felt like it would handle classic Visual Studio as well, but I didn't want to bother with the install.