[Bug 34166] Fullscreen flickering on Mac

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=34166

--- Comment #78 from Dr 4asm <ignas2526 at gmail.com> ---
(In reply to Henri Verbeet from comment #77)
> (In reply to Mike McQuaid from comment #73)
> > Given you officially support macOS as a platform, Apple haven't changed
> > this, you recommend Homebrew as an installation method and there's a
> > non-trivial number of Homebrew Wine users: is there any way you could
> > consider merging this patch? As mentioned before I don't feel Homebrew
> > maintainers are suitable for deciding whether a Wine patch is appropriate or
> > not and getting things upstream benefits other macOS package managers and
> > those who build from source on that platform. Thanks again!
> 
> I'm afraid I'll have to disappoint, it's really up to Apple to fix this.
> There may be architectural changes that may mitigate the issue in the
> future, but I can't promise that.
> 
> The thing is that the Apple OpenGL implementation has many more bugs and
> quirks than just this one, and while the individual workarounds for those
> may seem innocent enough on their own, those quickly add up to something
> unmaintainable. The other consideration is that Wine is primarily a Free
> Software project, and has comparatively few users and developers on MacOS.
> That means that even if we did include those kinds of workarounds, it would
> be relatively easy to inadvertently break them again.

While it might be Apple's fault, in the end, some applications are pretty much
unusable in the wine on the Mac because of this. To be on a same page, I invite
you to try to run one of the affected apps for couple minutes with it
flickering at 20+ fps. I hope you don't have photosensitive epilepsy.

I've been following this bug for a long time, and as far as I can tell, it is
not being fixed due to some ego issues. At least some of the developers here
seem to be obsessed with creating this clean, pure implementation that has no
"workarounds"... What you're forgetting, is that we're living in an imperfect
world, where every single OS is flawed. No matter how hard you try, at the end
of the day, you will have to write code to deal with OS's quirks. Unless, you
don't care about your software being usable. At this point, you should ask
yourselves: are we creating something for real users out there or are we
creating something to show off? It seems like the goal here is the second.

As for lack of MacOS users, well, if the software is unusable, why do you
expect it to have users?

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.