The new super food - why is it so healthy?


As of now there are basically three well-known solutions to run Windows software in Linux environments. Have a look in the following table how they compare to each other in terms of making Windows software available for users running mainly Linux environments:


Solution
Dual Boot
Virtualization
Wine
Costs
Windows license

Windows license

for some solutions: Virtualization license

free
Integration with the host system
N/A
host file system/hardware is isolated and (partially) passed through shared mount protocols/abstraction layers
seamless
Performance
native
reduced, especially for 3D GFX and file I/O
near native, also for 3D GFX
Requirements
separated installation
memory overhead, fixed resource allocations
many functionally complementary versions, many dependencies
Functionality of installed application
as good as it gets
nearly as good as it gets
depends on windows software and wine version / configuration
Effort maintaining many applications
as good as it gets
low effort to make apps work, but resource-hungry and often bad usability, system updates may break VMs
high effort to make apps work, high effort to not break apps due to system upgrades or newly installed apps
Effort maintaining one application
ridiculously high
still too high
justifiable if the application is important


Now how do Dolmades compare to that?


  • Costs: no licensing fees required
  • Integration with the host system: seamless , but file system is isolated. Files on the host system can be made available by disk drive binds.
  • Performance: near native, 3D support lacks behind Windows
  • Requirements: non-privileged Linux user account, Python 2.7
  • Functionality of installed application: if you happen to make a software run using any version of wine there is currently no better way to preserve its functionality across system upgrades.
  • Effort maintaining many applications: Applications exist as separated dolmades with independent configuration and system files each. System upgrades and newly installed software won't affect them.
  • Effort maintaining one application: If you find an existing recipe for the application it is as easy as it gets. Just download and install it. If the application is new, you can develop a recipe using the required ingredients, cook your application and start using it. As soon as it seems to work reliably you can share the recipe.


But wait - aren't only a few apps supported yet?

Yes indeed. And there is still a high effort to install a particular app and make it work well as dolma. But as soon as it is done, a recipe specific to that app has been made and can be published so that other users just need to download the ready-to-use container.






GITHUB
code


RELATED

wine  udocker  proot


IMPRESS