I was hoping this was a treatise on the history of wine production.
Dunno if that's as likely on Hacker News.
How Wine works 101
101–110 of 188 posts
Re: How Wine works 101
#102What a great article. I never had anything to do with wine, this was a joy to read.
Re: How Wine works 101
#103Earlier quoted context omitted.
According to Raymond Chen, this usually happens when software relies on undocumented APIs or undefined behavior. When Windows removes undocumented APIs or changes behavior not covered by the documentation, such apps break and people blame Microsoft. For example, I remember one app used to programmatically find some kind of "Print" menu in Windows' desktop environment and call it to implement printing functionality. W…
Most old games do not work because of old graphics apis. Wine emulates these apis on top of modern graphic apis. Windows users usually need to use wrappers, or wined3d from wine.
Yeah, 3D games using DirectX 8- are a shitshow on Windows Vista+...
Re: How Wine works 101
#104Earlier quoted context omitted.
'Recently' meaning about the past 10 years or so. Windows 8 broke a lot of software for me that runs in Wine.
In 2016 I was asked to install some software on a WinSvr2012R2. I was forced to install it on my Win8.1 tablet first, because the 16-bit stub didn't work on x64 2012R2. After install I copied the files to the server and the software brazenly showed "XXX for Windows 95" in the Help->About. On a 2012R2 x64 server. In the year 2016. There was (and is) a lot of shit which developers did wrong ( including writing directly…
Yeah, I have Windows 98 in a VirtualBox for those 32 bit programs using a 16 bit installer...
Re: How Wine works 101
#105Re: How Wine works 101
#106I SO expected this to be about the basics of wine making (the beverage) and kind of let me down after opening the link.
Please somebody make wine-making 101
Re: How Wine works 101
#107Earlier quoted context omitted.
The point of Wine is to run older Windows software. Who needs the most modern versions, just pays for MS Windows. Windows, like DOS before it, adapts to run certain apps more efficiently, to sidestep their bugs, or to fulfill their assumptions which generally do not hold. I suppose Wine does a lot of the same. It pays a lot of attention tp running old(er) popular software smoothly. I suppose Wine has more adjustments…
> just pays for MS Windows. Paying for MS Windows is not a problem. If I could just throw money at Microsoft and have all the apps I need running on Linux, I would have. I suspect many people (and specially orgs) would have done that too. Incidentally, I have a copy of MS Windows. I just _don't want to boot Windows_ > It pays a lot of attention tp running old(er) popular software smoothly. Nah. It pays attention to p…
Oh wow, Stadia is already dead ?! Google has "outdone" themselves !
Re: How Wine works 101
#108I SO expected this to be about the basics of wine making (the beverage) and kind of let me down after opening the link. Please somebody make wine-making 101
This is a topic worthy of acoup.blog, who did extensive reviews of the history of how steel, bread and clothing were made.
Re: How Wine works 101
#109How did you generate the screenshot of the Windows/Linux call stack? It seems to be running on Windows, from the GDI-style font rendering and Visual Studio-style appearance; is it Visual Studio or a custom program, and can you run the debugger on Linux?
This is Visual Studio with the Stadia debugger extension (https://github.com/googlestadia/vsi-lldb). It runs LLDB on Windows and attaches to a process running on a remote Linux machine (Wine in this case). We have a couple of custom patches to LLDB to support Wine, which are not open source yet, unfortunately. The Wine support is not perfect, but most things work (call stacks, breakpoints, stepping though the code, etc).
Re: How Wine works 101
#110Earlier quoted context omitted.
MS are profit motivated (by definition) and Wine is functionality motivated (again by definition). MS are currently hell bent on getting you onto a cloud subscription for Windows as a service (WAAS) because that is their current business model. The Wine project is hell bent on delivering functionality that you want and they think you might want. Wine is less about shuffling the start menu to the middle of the taskbar…
Wine has been affected by profit too. Nobody remembers CodeWeavers? Let alone plenty of distros are for-profit and use it as a means to advertise their game-playing capabilities.
> Nobody remembers CodeWeavers?
Haven't they been contracted by Valve to work on Proton?