3 ms·
His approach is a bit different as he is shimming 16 bit APIs to their 64-bit equivalent. Wine reimplemented them to run on top of a POSIX environment. His app
by mmastrac 10y ago
His approach is a bit different as he is shimming 16 bit APIs to their 64-bit equivalent. Wine reimplemented them to run on top of a POSIX environment.
His approach will result in higher fidelity for apps as they are basically running on Win64, just with a 16-bit virtual machine driving it.
Wine apps running on Windows would likely feel non-native as the UI components are reimplemented from scratch.
- TazeTSchnitzel 10y agoWell, the UI components in Wine feel like Windows, just not like Windows 10.
- leonatan 10y agoWindows 98 perhaps. 2000 if generous.
- TazeTSchnitzel 10y agoYes, they have the “Windows Classic” look and feel.
- userbinator 10y agoI find it a bit amusing that were they to "update" their look to that of the flat Windows 8+ UI, it would probably entail the removal of a lot of code. ...and yet even on a 25MHz 386, no one complained about the slow drawing speed of the "fancy" 3D buttons in Win3.x.
- yathern 10y agoWell, modern flat design generally also includes a much more animated interface, which would probably entail the addition of much more code. And I don't think the drawing speed of buttons was ever a very strong reason for the rise of flat design - though I completely understand your distaste for it.
- JonathonW 10y agoWine actually has (mostly) functional theming support-- point Wine to a .msstyles theme DLL and it'll draw themed controls (rather than the Windows Classic style default). They just don't ship a theme with Wine; understandable for licensing reasons (they can't distribute Microsoft's designs), but it means that Wine looks like Windows 2000 out of the box.
- nitrogen 10y agoThe .msstyles support in Wine was terribly slow last time I tried it. Has it improved?