Unfortunately, the hardware you use still matters. Hardware manufacturers just don’t care to invest in Linux support, so it’s basically all community driven. The community has done amazing work in spite of that, so a lot if hardware works, but unfortunately, if you want to make a permanent change to Linux, it really pays off to be mindful of that goal when you’re picking components. AMD hardware tends to work better than alternatives in my experience, especially in the GPU, but I don’t use and so can’t speak to any other peripherals.
But I’ve had great luck with some of these things. I used to RDP into my Linux desktop all the time just fine, including from a Windows laptop. I haven’t really played with tiling window managers, but I know there are some powerful ones out there if you’re willing to take the time to learn how to config to your personal taste. I think i3 and xmonad are common for X11 and Hyprland for Wayland. Font and display scaling is highly dependent on the desktop environment you use. I want to say GNOME and KDE have made big strides here in recent years as they try to become adaptable to tablets, phones, and other small hardware, so if you haven’t tried that in a long time, it may be worth a look again.
For specific software you just can’t live without like Teams, there’s two option. WINE is the less resource intensive option, and it’s basically a translation layer that turns Windows system calls into Linux ones, and it’s really good these days. In the rare (for me) case that WINE doesn’t work, if you have the spare resources on the machine, you can use a virtual machine running Windows. If you really need that VM to work fast, you can set up hardware pass through so the VM gets direct access to it. That’s generally pretty easy with CPU cores and RAM, but if you need to pass through the GPU for anything, that can get complicated fast last I knew. And of course, a VM is a heavy option for just making Teams work, but if you want on Linux bad enough, it may become worthwhile.
Really, I feel like the only thing here that should be insurmountable is drivers. Maybe Windows software that you need if you’re really unlucky, but most of that works well these days in my experience.
Unfortunately, the hardware you use still matters. Hardware manufacturers just don’t care to invest in Linux support, so it’s basically all community driven. The community has done amazing work in spite of that, so a lot if hardware works, but unfortunately, if you want to make a permanent change to Linux, it really pays off to be mindful of that goal when you’re picking components. AMD hardware tends to work better than alternatives in my experience, especially in the GPU, but I don’t use and so can’t speak to any other peripherals.
But I’ve had great luck with some of these things. I used to RDP into my Linux desktop all the time just fine, including from a Windows laptop. I haven’t really played with tiling window managers, but I know there are some powerful ones out there if you’re willing to take the time to learn how to config to your personal taste. I think i3 and xmonad are common for X11 and Hyprland for Wayland. Font and display scaling is highly dependent on the desktop environment you use. I want to say GNOME and KDE have made big strides here in recent years as they try to become adaptable to tablets, phones, and other small hardware, so if you haven’t tried that in a long time, it may be worth a look again.
For specific software you just can’t live without like Teams, there’s two option. WINE is the less resource intensive option, and it’s basically a translation layer that turns Windows system calls into Linux ones, and it’s really good these days. In the rare (for me) case that WINE doesn’t work, if you have the spare resources on the machine, you can use a virtual machine running Windows. If you really need that VM to work fast, you can set up hardware pass through so the VM gets direct access to it. That’s generally pretty easy with CPU cores and RAM, but if you need to pass through the GPU for anything, that can get complicated fast last I knew. And of course, a VM is a heavy option for just making Teams work, but if you want on Linux bad enough, it may become worthwhile.
Really, I feel like the only thing here that should be insurmountable is drivers. Maybe Windows software that you need if you’re really unlucky, but most of that works well these days in my experience.