Comments by "OpenGL4ever" (@OpenGL4ever) on "Linux Mint 22: Excellent Distro for Windows Users" video.
-
7
-
@encycl07pedia- When installing Windows, you can clearly specify which partitions it should use for Windows. If you make mistakes, it's your own fault, which is the typical problem in front of the screen. Windows won't delete your Linux partition if you don't want it to, and Windows won't do that in everyday use either.
All modern Windows systems, from Windows 10 to Windows 11, belong to the Windows NT family.
The only Windows that always installed its data on the first partition it could find were the Windows versions of the Windows 9x/Me series. But these don't belong to the Windows NT family.
A VM has other disadvantages. For example, it requires a dedicated GPU for the guest system if you need high-performance 3D graphics. This is associated with extra costs and there is always a layer in between. Virtual I/O is also required. And the boot times to the guest system are also longer.
If the host system fails, you cannot even use the VM's guest system.
With a dual boot setup, you still have the other OS available, even in extreme emergencies if one should cause problems.
3
-
@encycl07pedia- I disagree. I have use for both. Dual booting and VM. In this case, I don't use GPU pass through for the VM (see below), but instead forward the graphics commands to the host system. For the purposes for which I use the VM in this case, this is completely sufficient. I don't play games in a VM.
The boot time is negligible, if I choose to boot into Windows, then the computer will run on Windows for a few hours. The same goes for Linux. I don't constantly switch between operating systems every 30 minutes or so.
I also plan my updates. If, for example, I want to play games on Windows at the weekend and haven't booted Windows for the last 14 days, I boot Windows the night before and let the updates install while I do something else in the meantime. From surfing the internet, watching Netflix on Windows or just reading a book, there are lots of options. That way there are no surprises the next day if I want to play games, for example. And to come back to boot time, games are real time-wasters. I don't start and play them for 30 minutes. I allow myself at least 3-8 hours for the games at a selected weekend, for example, and that's why the 20 seconds of booting are completely irrelevant to me.
You have no idea. You're also forgetting an important point. My CPU doesn't have an integrated iGPU. I would have to put two dedicated graphics cards in the computer just so I can use GPU pass-through for the VM to have max performance and still have an image for the host system. That would be a complete waste of electricity. Electricity is expensive here. It also heats up the apartment unnecessarily in the summer.
And the full GPU performance is never available on the host system if you have an iGPU there or use something cheap as a dedicated GPU just for the host system. And buying two dedicated high-end GPUs would be a waste of money and also a waste of performance because you would have two GPUs but wouldn't even be able to use SLI.
Due to dual booting, I get the maximum performance from my dedicated GPU under both Windows and Linux. Dual booting is simply the much smarter step here. And if I'm immersed in a game for 5 hours, then I have absolutely no reason to switch from the VM to the host system.
3
-
2
-
@encycl07pedia- There is nothing wrong with using both, Dual boot and VM.
But what you're not realizing is that you're making things even more complicated for the user and not working with virtual machines. You either pass the hardware through to the VM, which allows you to use the original drivers on Windows running as a guest system, but then you can't use them for the host system. Or you forward the requests to the host system and the host system then has to implement support for the hardware with its own drivers, and then you have the problem that one or other feature doesn't work, because it is not supported by the driver. This problem doesn't exist with dual booting, and that's one of the main reasons why I dual boot. Of course, I realize that you don't know all these details, because you've made it clear that you don't know much about computers.
If you want to pass the hardware natively to the VM so that you can use the manufacturer's original drivers, then the VM needs its own hardware.
For example, you can pass a USB port to the guest system. Then you can connect a gamepad there and use it with the guest system's native drivers. The host system then doesn't need to have driver support, but you then can't use the gamepad for the host system either. If you wanted to do that, you would either have to stop this USB port forwarding or use a second gamepad for your host system or re-plug it on another usb port. The same applies to keyboard and mouse when using passing through natively.
This is not so serious for input devices because you can do without the native pass through for common devices or when driver support is good enough on the Host System. But with a dedicated graphics card it means that you have to connect its graphics output to the screen and if your screen doesn't have two inputs between which you can switch between the signal from the dedicated graphics card and the signal from graphics card that is used by the host system, then you can't use this screen for the host system or you have to buy a hardware switch or use two screens, which all costs extra money.
Such problems are all eliminated with dual booting. These problems simply do not exist when dual booting.
2
-
2
-
2
-
1
-
1