Live data from Hacker News

Wine 2.0 released

winehq.org

291–300 of 314 posts

Re: Wine 2.0 released

#291

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?

I use it all the time (in macOS and Linux) for running MikroTik's[1] configuration tool (named "winbox.exe").

[1] http://www.mikrotik.com/

Re: Wine 2.0 released

#292

Earlier quoted context omitted.

Ableton runs pretty well from wine too. Almost no messing around

bitwig has a native linux version.

I really want to start using bitwig (it seems like Ableton, but better), but I can't afford it. In all honesty, I'm using a cracked version of Ableton that I found man years ago, but I can't really find (or securely test) bitwig cracks.

Re: Wine 2.0 released

#294
post #162
post #136

Earlier quoted context omitted.

The Linux root is more insulated if your application is in a VM, but running other Windows services broadens the attack surface.

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

I've never tried this, but I know that Wine doesn't use VT-x so I think it would work better than nested VMs.

I don't know how much sandboxing Wine provides, so it might not be necessary to do this.

Re: Wine 2.0 released

#295
post #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.

Interestingly, CodeWeavers appears to be part of the reason in 2002 why Wine changed its license from MIT to LGPL. They were concerned about the fact that CodeWeaver's fork of Wine was proprietary.

(Sources: https://en.wikipedia.org/wiki/Wine_(software)#History https://www.winehq.org/pipermail/wine-devel/2002-February/00...)

CodeWeaver's Wine variant still seems to be proprietary according to Wikipedia -- I wonder what made the relationship between CodeWeavers and Wine evolve.

Re: Wine 2.0 released

#296
post #295
post #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.

Interestingly, CodeWeavers appears to be part of the reason in 2002 why Wine changed its license from MIT to LGPL. They were concerned about the fact that CodeWeaver's fork of Wine was proprietary. (Sources: https://en.wikipedia.org/wiki/Wine_(software)#History https://www.winehq.org/pipermail/wine-devel/2002-February/00... ) CodeWeaver's Wine variant still seems to be proprietary according to Wikipedia -- I wonder w…

While there is some proprietary glue, all changes to the Wine code are (as they have to be) open source.

Re: Wine 2.0 released

#297

Earlier quoted context omitted.

Are you sure that's going to work? I don't think you'll be able to take full advantage of your graphics hardware that way. (Last I checked, Virtualbox and friends refused to allocate more than 256MB of VRAM... so I could play Duck Game and no more.)

Good question. I was thinking it'd be fun to benchmark an application running on Windows vs. that same application running on Wine running in the Ubuntu Userspace in Windows. I'd have to guess it'd be at least a few times slower.

That would make since, considering the overhead involved in translating the syscalls twice. It would be really interesting to see if/how the native Windows syscalls differed from the ones coming out of the Wine->WSL pipeline.

Re: Wine 2.0 released

#298

Earlier quoted context omitted.

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 think…

Nowhere did I say that the WINE folks should support old versions.

I said that the information in the user report could be relevant and useful to people who still use that version, even if it's unsupported.

These are informational reports of "this app behaves this way under version x." So, and this is isn't about supporting an old version, this is about allowing or not allowing information about old versions in a database.

I don't think more information is harmful to the users, especially when it can help them make an informed decision about whether or not they must upgrade in order to be able to run a particular app.

Re: Wine 2.0 released

#299
post #295
post #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.

Interestingly, CodeWeavers appears to be part of the reason in 2002 why Wine changed its license from MIT to LGPL. They were concerned about the fact that CodeWeaver's fork of Wine was proprietary. (Sources: https://en.wikipedia.org/wiki/Wine_(software)#History https://www.winehq.org/pipermail/wine-devel/2002-February/00... ) CodeWeaver's Wine variant still seems to be proprietary according to Wikipedia -- I wonder w…

I believe it was actually that a different fork of Wine was not contributing back which caused the license change. I want to say it was Cedega but memories are hazy at this point (since I'm an outside observer).

Re: Wine 2.0 released

#300

Earlier quoted context omitted.

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…

Debian stable's Wine is often fairly old. I wish there was an easier way to get a newer Wine on stable. They're rejecting your reports because the issues are often fixed in newer versions - someone would have to re-confirm your reports on a newer version.

> They're rejecting your reports because the issues are often fixed in newer versions

Sure, newer versions fix bugs from older versions. But they don't delete/archive the old reports after a new release, so the reports that are there are already a mix of supported and unsupported versions anyway.

So, I don't see the harm in accepting new reports against older versions, particularly when old versions are still found several major distros (particularly the LTS versions of those distros)

Post reply on HN