3 ms·
This uses Wine, which isn’t emulation. Also since when were containers more “bloated” than emulation? The whole point of containers is that they don’t need to
by hnlmorg 3y ago
This uses Wine, which isn’t emulation.
Also since when were containers more “bloated” than emulation? The whole point of containers is that they don’t need to virtualise the entire stack because they are reusing parts of the host stack.
- actionfromafar 3y agoA rose by another name… that Wine is not an emulator is a good tagline, but it emulates Windows behaviour really well.
- pareidolia 3y agoIt's a runtime environment, like the JRE or Mono CLR. By your logic, the JRE is an emulator because it has a "java virtual machine."
- xcv123 3y agoWINE is not a VM though. It is an implementation of the Windows API. The Wine documentation admits that it is emulating the Windows API. https://wiki.winehq.org/Wine_Developer%27s_Guide/Architecture_Overview#Foreword https://wiki.winehq.org/Wine_Developer%27s_Guide/Architectur... Of course there is no hardware emulation, so all Windows binary code is running natively with no performance drop. That's why it was called WINE. But still there are two meanings of the word. Hardware emulation or OS emulation at API level.
- hnlmorg 3y agoThese two meaning are a little like how “theory” can mean different things to scientists vs non-scientists. In the context of computers, “emulation” has a specific meaning and one which isn’t applicable to WINE.