Live data from Hacker News

Wine 7.0

winehq.org

141–150 of 153 posts

Re: Wine 7.0

#141

I use Wine for one thing: running MusicBee. It's a pain in the ass to get it working 100%. Every time I've tried to upgrade past wine 4.x it completely breaks my MusicBee wine prefix, so I've locked the version and will never upgrade. Ultimate goal is to wait until any native Linux music player is even 10% as good as MusicBee.

MusicBee was one thing I looked over in my switch to Linux a couple months ago. In my head, I could simply find any other music player for Linux and be on with my life. But I found that MusicBee had so much ancillary functions that had made their way into my music management flows over the years that were lacking in other players. I still haven't bothered to find another player, but I have been working on creating new flows using beets, which is probably a better approach as it separates the concerns of managing and playing my music.

Re: Wine 7.0

#142
post #124

Earlier quoted context omitted.

It's a 2000 page spec that links to other specs (eg JPEG, PNG). It is a turing complete document format that can run arbitrary code without a sandbox. It is a mix of a binary and text format (some opcodes are in binary, some in text which just why?). All in all, it is a format designed to be incredibly hard to implement so people just give up and pay adobe.

Other than some stupid feature of it (like some of the ones you mentioned, maybe also forms), I really don’t think it is too hard to implement - there are plenty of open-source pdf reader libraries.

From what I've seen, most of the libraries out there are some mix of incomplete and slow. From my testing (from a few years ago), most of them supported about 80% of the documents you would see in the wild. Good support for FDF (form fillable PDF) was really bad pretty much across the board.

Re: Wine 7.0

#143

I use Wine for one thing: running MusicBee. It's a pain in the ass to get it working 100%. Every time I've tried to upgrade past wine 4.x it completely breaks my MusicBee wine prefix, so I've locked the version and will never upgrade. Ultimate goal is to wait until any native Linux music player is even 10% as good as MusicBee.

Spotify runs fine on Linux and you'll free up a ton of disk space!

Re: Wine 7.0

#144
post #54

I have a patch that adds AF_UNIX support (added in Windows 10). It needs help to get it upstream. https://www.winehq.org/pipermail/wine-devel/2021-May/187049....

Nice, maybe worth having a test in the test suite ?

As another commenter wrote opening a bug is a good idea, mention a program this helps get working too.

Re: Wine 7.0

#145
post #139

Earlier quoted context omitted.

Do you have any evidence for that claim?

It's not a claim but a rhetorical question, hence the question mark...

A rhetorical question is a question asked to make a point, rather than get an answer.[1] A point, aka a claim here.

But maybe you meant a non-rhetorical question. In which case, it would be clearer if you started it with a "Maybe" - if your intent was to genuinely ask it as a question.

[1] https://www.bbc.co.uk/bitesize/topics/zmfc7ty/articles/z7dyv...

Re: Wine 7.0

#146
post #3

I recently used Wine to run Office 97 on Debian, just for old time's sake. I ended up liking it so much that I now use it for my word processing and spreadsheet tasks. This classic version is feature complete to me. Wine ensures it lives on, long past its support date and on an alien operating system. And clippit says hello! Screenshot for the curious: https://imgur.com/a/GmVUAfC It shows Word 97 on Linux editing a l…

How do you even get a legit copy of Office 97 these days?

Independent of copyright term reductions, I think you really should have to continue to activiely distribute something in order to retain copyright. Abandonware should be equivalent with public domain.

Re: Wine 7.0

#147
post #88
post #22

Earlier quoted context omitted.

This is a semantics debate, but it kind of is an emulator. Instead of emulating a CPU, it emulates the Windows API. That's obviously a major difference: One is inherently slower, while the other is inherently more complicated. WINE originally stood for "Windows Emulator", but for trademark reasons it was changed to "Wine Is Not An Emulator". That's giving you some mixed messages now, isn't it? [edit] I just checked W…

It implements the Windows API.

And the Windows API is defined as "whatever Windows does", which Wine emulates.

Re: Wine 7.0

#148
post #25

So as a Wine end-user, it looks like this release means no more having to have multiple wineprefixes to support both 32/64 bit applications, and also no more need to ensure libraries like libpng zlib etc are installed, either 32 or 64 bits? That seems quite nice.

> So as a Wine end-user, it looks like this release means no more having to have multiple wineprefixes to support both 32/64 bit applications

WoW64 prefixes have been possible for a long time.

> and also no more need to ensure libraries like libpng zlib etc are installed, either 32 or 64 bits? That seems quite nice

That seems to be the plan, but according the release notes there are still some native 32-bit libraries that will be needed.

Re: Wine 7.0

#149

Isn't linux still falling farther behind? If I want to use my linux desktop to run some of the gazillion inexpensive apps written for the computerphones or any of the bazillion high-prestige apps written for the Apple desktops, what are my chances?

Apple desktop: slim chance at best. There's a similar effort to port cocoa. iOS: Forget it. Android: Apps that work on x86 smartphones run easily on x86 desktops; apps that only work on arm phones require emulation on x86 and it's substantially more complex to get working, but you can do it.

> Apple desktop: slim chance at best. There's a similar effort to port cocoa. iOS: Forget it.

For reference, the macOS not-an-emulator is Darling [0] but yes, there does not seem to be enough interest for it to catch up any time soon.

[0] https://www.darlinghq.org/

Re: Wine 7.0

#150
post #13

I use Wine for one thing: running MusicBee. It's a pain in the ass to get it working 100%. Every time I've tried to upgrade past wine 4.x it completely breaks my MusicBee wine prefix, so I've locked the version and will never upgrade. Ultimate goal is to wait until any native Linux music player is even 10% as good as MusicBee.

Which features do you desire? What is your ideal music player?

1. Main music browser pane should be in column format (think: "excel spreadsheet" with configurable columns of metadata), with a search bar that filters on any visible column or advanced metadata search.

2. Separate "Now playing" pane so I can browse in the main page without affecting what is currently playing (lots of players break this). It's basically a separate, anonymous playlist.

3. Support for custom id3 tags. These have been around for decades but only have limited support. Some players do a half assed job, others don't bother at all, some don't even support the "comment" field. MusicBee let's me define tags and use them as columns in the music browser, Now Playing view, smart playlists, searches etc.

That's it. Decent playlist management would be great but I don't find MusicBee particularly outstanding here either. What I'd like is the ability to tag my playlists with the year, moods and comments - like virtual compilation albums.

I don't use my music player for stupid visualisations. I don't care about lyrics or album art. It's 100% about finding music and creating a play queue. If I like the queue I can save it as a new playlist. That's it.

Post reply on HN