this post was submitted on 22 Jul 2023
11 points (100.0% liked)
Technology
37717 readers
445 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Sounds like an esoteric thing to do.
To begin with; Teams isn’t a very friendly thing to run in the first place.
Then you want to run a virtualized windows instance, multiple maybe even, so that you can run Teams in these instances?
Would that be x64 windows? Virtualized, running on Rosetta, on an ARM CPU?
I guess if your only goal is to find out, sure.
But if you want to virtualize windows, why start with a mac?
I know someone who took a CPU out of the socket with the system “running” and then put it back in and resumed operations.
Sure, it can be done. But everyone else will just unplug the power and be done with it.
In the meantime I can wholeheartedly recommend Apple Silicon, but Microsoft’s software is still the worst stuff that I run on my mac.
Also, you can just use Teams from the browser if you don’t need any integrated features.
It is. I did wonder given I run the MacOS version on my M2 Mac mini just fine.