by Bakoes » Thu Feb 05, 2026 2:29 pm
From what I understand now... (not tried yet)
[Eventually I will try it, but that could take a while...
If there's anyone who tried it, please let us know ♥.
Maybe the MM team could try it, and make it more compatible with Wine/Bottles...]
it should already work on Linux with ► "Wine" or even better with ► "Bottles" .
(Bottles is somehow a part of Wine, but it creates an isolated Wine version,
for every app that you install,
so it will be more stable even after a Wine update)
▬ And this isn't a Virtual Machine.
Then you could try installing ► "WinBoat".
Or a Windows Virtual Machine.
☻AI Overview:
Running Windows apps on Linux involves a trade-off between performance (Wine/Bottles) and compatibility (VM/Winboat).
• Wine and Bottles offer high performance and low overhead but may struggle with complex apps.
• Winboat (and similar containerized solutions) uses a hidden VM to provide near-perfect compatibility, while
• Windows Virtual Machine (VM) is the most reliable, secure option for complex software, though resource-heavy.
☻Comparison Breakdown:
◘ Wine (Compatibility Layer):
Best for: Gaming (via Proton/Lutris), lightweight utilities, and older apps.
Pros: High performance, no overhead of a full OS, directly accesses hardware.
Cons: Low compatibility for complex/modern apps; can be difficult to configure.
◘ Bottles (User-Friendly Wine):
Best for: Beginners wanting to manage Wine without using the command line.
Pros: Manages dependencies (WineTricks) automatically, isolates apps in "bottles".
Cons: Still limited by Wine's underlying compatibility.
◘ Winboat (Containerized Windows):
Best for: Running stubborn apps that fail in Wine while still having them look "native" on the desktop.
Pros: Runs a full Windows environment (in Docker/KVM) for high compatibility, but streams apps to the Linux desktop.
Cons: Requires 4GB-8GB+ RAM, higher overhead than Wine.
◘ Windows Virtual Machine (VM - VirtualBox/VMware):
Best for: Full-featured Microsoft Office, specialized software, or when maximum stability is required.
Pros: 100% compatibility, total isolation (secure).
Cons: Highest resource usage (RAM/CPU/Disk), slow startup.
☻Summary Recommendation:
Try Bottles/Wine first for games and simple tools.
Use Winboat for complex software (e.g., Office) when Wine fails.
Use a Virtual Machine for maximum reliability if you have strong hardware.
From what I understand now... (not tried yet)
[i][color=#80BFBF][Eventually I will try it, but that could take a while...
If there's anyone who tried it, please let us know ♥.
Maybe the MM team could try it, and make it more compatible with Wine/Bottles...][/color][/i]
it should already work on Linux with ► "Wine" or even better with ► "Bottles" .
(Bottles is somehow a part of Wine, but it creates an isolated Wine version,
for every app that you install,
so it will be more stable even after a Wine update)
▬ And this isn't a Virtual Machine.
Then you could try installing ► "WinBoat".
Or a Windows Virtual Machine.
☻AI Overview:
Running Windows apps on Linux involves a trade-off between performance (Wine/Bottles) and compatibility (VM/Winboat).
• Wine and Bottles offer high performance and low overhead but may struggle with complex apps.
• Winboat (and similar containerized solutions) uses a hidden VM to provide near-perfect compatibility, while
• Windows Virtual Machine (VM) is the most reliable, secure option for complex software, though resource-heavy.
☻Comparison Breakdown:
◘ Wine (Compatibility Layer):
Best for: Gaming (via Proton/Lutris), lightweight utilities, and older apps.
Pros: High performance, no overhead of a full OS, directly accesses hardware.
Cons: Low compatibility for complex/modern apps; can be difficult to configure.
◘ Bottles (User-Friendly Wine):
Best for: Beginners wanting to manage Wine without using the command line.
Pros: Manages dependencies (WineTricks) automatically, isolates apps in "bottles".
Cons: Still limited by Wine's underlying compatibility.
◘ Winboat (Containerized Windows):
Best for: Running stubborn apps that fail in Wine while still having them look "native" on the desktop.
Pros: Runs a full Windows environment (in Docker/KVM) for high compatibility, but streams apps to the Linux desktop.
Cons: Requires 4GB-8GB+ RAM, higher overhead than Wine.
◘ Windows Virtual Machine (VM - VirtualBox/VMware):
Best for: Full-featured Microsoft Office, specialized software, or when maximum stability is required.
Pros: 100% compatibility, total isolation (secure).
Cons: Highest resource usage (RAM/CPU/Disk), slow startup.
☻Summary Recommendation:
Try Bottles/Wine first for games and simple tools.
Use Winboat for complex software (e.g., Office) when Wine fails.
Use a Virtual Machine for maximum reliability if you have strong hardware.