Live data from Hacker News

Wine 7.0

winehq.org

51–60 of 153 posts

Re: Wine 7.0

#51
post #21

Earlier quoted context omitted.

Wine Is Not an Emulator, so I doubt it will be able to run x86 apps on ARM.

> - The new Apple Silicon Macs are supported, including running x86-64 binaries under Rosetta 2. Depends which ARM :)

Apple Silicon has special support for running ARM code with the "Total Store Order" memory model of x86.

JIT-compiling emulators for other ARM processors otherwise need to be stuff the code full of memory fence instructions to be able to utilise multiple cores properly. Optimising those away can be hard.

Re: Wine 7.0

#52
post #19

Earlier quoted context omitted.

Excel, Word and PowerPoint run as well as they did on Windows. All the main functionality is very stable. Wine even integrated the icons and mime-types into my DE. It is only very occasionally I hit any critical error. It has only happened when trying something obscure, like "Microsoft Maps for Excel". I haven't tried Outlook 97 yet. But poor old Access won't even get off the ground. I'm guessing due to some ODBC dri…

Interesting. My main use case for using Word would be for my CV. Since I don't want it to render a single bit different than on a recruiting manager's screen. Unfortunately PDF still seems to be a bit of a disadvantage in some cases.

This doesn't quite make sense to me. Sending your Resume in .docx is kind of a terrible idea, and I've seen countless people running mainstream Windows version getting bitten by this. On top this, in my experience it's *much* easier for me as an interviewer to review your resume in PDF rather than docx (even if I have access to MS Word or Google Docs). I have never seen any company or recruiter (in the US) who prefers docx but I've seen multiple companies (including my own) that prefer PDF.

So, someone going out of their way to type their resume in wine word, only for it to be a scrambled mess... I would strongly recommend you not to do this. If you're emailing your resume and you absolutely want to go ahead with your plan, please consider adding both the pdf and docx. Good luck!

Re: Wine 7.0

#53

> Once the remaining modules are converted to PE, this will make it possible to run 32-bit applications without installing 32-bit Unix libraries. That sounds really amazing, I can't wait. That will really simplify using 32bit windows programs on a 64 bit OS.

Agreed, this reduces the need to keep 32-bit libraries around, though there are still native games that need that. May be something similar can be done for ELF libraries? That would be really cool.

Re: Wine 7.0

#55
post #9

I'm hoping that I'm correctly interpreting the WoW64 portion of the notes as meaning that I could run a 32-bit x86 Windows binary using the 64-bit Wine on ARM. I don't have a common need for this but I've had a couple of cases where I needed to test compatibility with something ancient and it would have been great to be able to install something in my development environment. In one of the cases, it was a 64-bit exec…

That probably won't work, WoW64 is running x86-64 on x86-32. You can combine Wine with QEMU to run x86-32 on AArch64 though.

Re: Wine 7.0

#57
post #7

Wow, an incredible amount of work/updates in this version. So glad to see a project like this continue moving forward in significant ways and I hope that these improvements bode well for things like Proton

I think it might be the other way around, Valve(proton) improves wine. Since they(valve) started working on game compatibility both wine, and dxvk has gotten a lot of love. Which continues to show that "real" enterprise investments are needed to advance some complex software, be it open source or not. Everything can't be done on a hobbyist basis.

As far as I know, Wine has not primarily been a hobbyist project for about 15 years, with the bulk of development being done by CodeWeavers, which uses it as the basis for their CrossOver product. I don't believe any of that has substantially changed with the advent of Proton, though I assume that Valve is paying CodeWeavers to also pay attention to Proton issues.

Re: Wine 7.0

#58
post #19

Earlier quoted context omitted.

Interesting. My main use case for using Word would be for my CV. Since I don't want it to render a single bit different than on a recruiting manager's screen. Unfortunately PDF still seems to be a bit of a disadvantage in some cases.

This doesn't quite make sense to me. Sending your Resume in .docx is kind of a terrible idea, and I've seen countless people running mainstream Windows version getting bitten by this. On top this, in my experience it's *much* easier for me as an interviewer to review your resume in PDF rather than docx (even if I have access to MS Word or Google Docs). I have never seen any company or recruiter (in the US) who prefer…

It is actually not for employment, but as I work as consultant / contractor I have these agencies between me and possible customers. They enjoy to edit out any contact information from CVs to act as middlemen. It sucks but does not reflect on the actual assignment in the end.

The idea to send it in both versions is actually very good. Thank you!

Re: Wine 7.0

#59
post #43
post #37

Earlier quoted context omitted.

I have never heard anyone have problems with a PDF CV. If that's a disqualification reason... I don't know. This is speaking of IT of course; if you are talking to a small business doing woodworking or whatever, all bets are off on what tech they can and cannot handle. I'd still bet on PDF more than doc(x), though, since maybe they don't have an expensive Word license but PDF should render in browsers.

It is actually not for employment, but as I work as consultant / contractor I have these agencies between me and possible customers. They enjoy to edit out any contact information from CVs to act as middlemen. It sucks but does not reflect on the actual assignment in the end.

Oh, okay yeah if they want to make edits, then giving them rendered output is indeed not the nice thing to do.

Re: Wine 7.0

#60

Earlier quoted context omitted.

I think it might be the other way around, Valve(proton) improves wine. Since they(valve) started working on game compatibility both wine, and dxvk has gotten a lot of love. Which continues to show that "real" enterprise investments are needed to advance some complex software, be it open source or not. Everything can't be done on a hobbyist basis.

As far as I know, Wine has not primarily been a hobbyist project for about 15 years, with the bulk of development being done by CodeWeavers, which uses it as the basis for their CrossOver product. I don't believe any of that has substantially changed with the advent of Proton, though I assume that Valve is paying CodeWeavers to also pay attention to Proton issues.

You're probably right, I don't know for sure but I believe Valve has employees working on these projects too, considering their investment in SteamDeck.
Post reply on HN