Live data from Hacker News

Wine 2.0 released

winehq.org

221–230 of 314 posts

Re: Wine 2.0 released

#221
I use Wine to run the 64bit Windows client of GuildWars2 on my iMac. It is more stable than the current GuildWars2 Mac client. Graphics performance isn't upto par, but I need stability more for events and dungeons. ArenaNet is still building a proper Mac client after Transgaming was taking over by NVidia.

Re: Wine 2.0 released

#222

Cool. I have to admit I haven't thought about Wine in a while because I can't think of any software I use that doesn't have a Linux version. What are people's use-cases nowadays?

Notepad++ - I once tried a bunch of Linux tools for editing a large text file (GBs), but none of them was performant and usable like N++ with Wine. This was a couple years ago, maybe things have changed since.

Re: Wine 2.0 released

#223

Cool. I have to admit I haven't thought about Wine in a while because I can't think of any software I use that doesn't have a Linux version. What are people's use-cases nowadays?

Notepad++ - I once tried a bunch of Linux tools for editing a large text file (GBs), but none of them was performant and usable like N++ with Wine. This was a couple years ago, maybe things have changed since.

For opening large files Sublime Text is my go-to editor. I haven't tried multiple GBs yet, but everything around 1Gb is going fine.

Re: Wine 2.0 released

#224
post #112

Wine is a great project, and truly 'is not an emulator'. It takes the main win32 APIs and they are reimplemented natively by posix means, GDI, USER32, ADVAPI, and so on. Time ago I run an experiment to port Wine to windows and run a notepad.exe on top of X11. After that I managed to wrap ActiveX components inside GTK2 bonobo components served on windows to insert them into Linux GTK apps so you could have UI-bound ne…

> Wine is a great project, and truly 'is not an emulator'. The Wine is not an emulator thing has an interesting history. It originally was officially called an emulator. The change was largely due to essentially marketing. The first suggestion for the "Wine Is Not an Emulator" language was made in 1993, over concern that "Windows Emulator" might run into trademark problems with Microsoft. That suggestion was by Bob A…

Found the /r/AskHistorians moderator. ;)

You're either crazy fast with your research, or you have really looked into this in some depth. Great write-up, thank you.

Re: Wine 2.0 released

#225
post #36

Earlier quoted context omitted.

Another non development way to contribute is on the appdb, testing compatibility - https://appdb.winehq.org/

Unless you run Debian stable (or probably any LTS distro), in which case they don't want your reports because "your software is too out of date". I find this attitude odd, because there are (at least) tens of thousands of wine installs under Debian alone. Surely the information is relevant and useful to people, even if the version is no longer officially supported. As a result, I've stopped wasting my time filing rep…

The Debian upstream is crazy out of date for almost everything. I get why, I understand the thinking, but they have a point.

At some point vendors - especially open source vendors with limited (volunteer) resources have to call time on supporting older versions. If you're running an unsupported version, and the new version is free to download and install, why would they go out of their way to support you? Their thinking is quite reasonable: it's your choice to use a distro that doesn't track releases frequently, pull down and build a later version from them.

And looking at the release notes 6000+ changes have probably happened since your release. How can they possibly support you and a few thousand Debian users in that scenario with such a small team so focused on so much work?

Re: Wine 2.0 released

#226
The biggest commercial contributor to Wine is CodeWeavers: https://www.codeweavers.com/

Fantastic and very sympathetic small company which offers a next-next-finish installation of Wine. Excellent if you run a Linux desktop in a corporate environment that expects the ability to run Windows stuff.

Re: Wine 2.0 released

#227

Earlier quoted context omitted.

> It's also a godsend for windows gaming on Linux here FTFY.

I'm pretty amazing at the Humble Bundle (DRM-free) and Steam selections for Linux; not just independent titles but some larger ones too. We've come a long way since Loki ports.

Keep in mind that some of them are using libwine ;)

Re: Wine 2.0 released

#228

I've been using computers my whole life, and a lot of the magic has been explained away. Wine is a project that continues to astound me. Grats to the Wine team, this is great!

It's like the Linux subsystem on Windows, but the other way around. :-)

With the exception that the Windows Subsystem for Linux can just rely on the opensource glibc et al. So, they basically 'only'[1] have to implement the syscall interface of the Linux kernel. They do not have to do any work to reimplement all the core Linux libraries in a compatible way.

Wine has a much harder task. Since the common Windows libraries are closed source and non-redistributable, the Wine project basically has to reimplement every API/ABI that Windows provides. This is a much larger and harder project.

It would be a nice gesture of Microsoft if they released some of the core Windows libraries as open source. But of course, that's not going to happen.

[1] This is of course much harder than it sounds.

Re: Wine 2.0 released

#229

Earlier quoted context omitted.

bitwig has a native linux version.

I'd imagine the main issue is VSTs.

There are some VST bridge programs that use WINE underneath. I haven't actually used any yet so I can't attest to their usefulness.

https://github.com/abique/vst-bridge https://github.com/phantom-code/airwave

Re: Wine 2.0 released

#230
post #204
post #162

Earlier quoted context omitted.

Any problems running Linux in a VM then Wine within that?

Kind of negates the purpose of even using wine. If your running a windows machine to run a Linux VM then you might as well install straight to Windows and not deal with the underpowered VM

>If your running a windows machine to run a Linux VM then you might as well install straight to Windows and not deal with the underpowered VM

Given the context, I don't believe mark-r was talking about using a Windows host for the Linux VM.

Post reply on HN