Re: Is XQuartz development abandoned?
Re: Is XQuartz development abandoned?
- Subject: Re: Is XQuartz development abandoned?
- From: Christopher Jones <email@hidden>
- Date: Fri, 31 Aug 2018 17:52:12 +0100
Hi,
> On 31 Aug 2018, at 5:14 pm, David <email@hidden> wrote:
>
> Jeremyhu is listed as the maintainer of xorg-server on MacPorts.
>
> does he spend more time working on that than XQuartz?
I cannot comment on Jeremy’s intentions w.r.t. XQuartz, but he has (a couple
times I think) mentioned on these mailing lists he was considering stopping
XQuartz releases and focussing exclusively on the MacPorts versions as the
primary distribution means.
I can comment on MacPorts, as I am a member. The X.Org <http://x.org/> related
ports are indeed more up to date there, and whilst Jeremy is listed as the
primary maintainer, there are a number of other interested parties (myself
included) who also contribute. In fact there are a number of things ongoing
right now looking to update a few X.Org <http://x.org/> components. This is the
big advantage compared to XQuartz, in that anyone who wants to can contribute
to it within MacPorts. X11 is certainly not dead in MacPorts, and I do
recommend anyone using the server to look to migrating to use the MacPorts
supplied version (port name is xors-server).
Chris
>
> David
>
>> On Aug 30, 2018, at 2:51 PM, email@hidden wrote:
>>
>> 4. Re: Is XQuartz development abandoned? (Filhol Alain)
>>
>>
>> Message: 4
>> Date: Thu, 30 Aug 2018 23:51:01 +0200
>> From: Filhol Alain <email@hidden>
>> To: email@hidden
>> Subject: Re: Is XQuartz development abandoned?
>> Message-ID: <email@hidden>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Here the answer I got from Jeremy Huddleston Sequoia on 02 Feb 2017.
>> I think we can be real pessimistic concerning X11 on macOS.
>>
>>> [AF] A question about slow dialogues with OpenMotif and XQuartz (much
>>> slower than with Linux).
>>>
>>> [JHS] <email@hidden>
>>> There is a known issue there, I believe with Yosemite and newer versions of
>>> macOS (maybe Mavericks+, maybe ElCap+, I forget exactly). The issue is
>>> below us in CoreGraphics and won't really be fixed on Apple's side as doing
>>> so would fix this case but cause bad performance penalties for every single
>>> other case out there. The real solution is to get XQuartz off of
>>> libXplugin and start using more modern macOS APIs (eg: finishing up
>>> libxcwm), but there's not really anyone actively working on that right now.
>>>
>>> [AF] Are you the only one involved in XQuartz developments ?
>>>
>>> [JHS] Yes, and I spend significantly less than 1% of my time on it ...
>>> barely enough to just pull in upstream changes, build, and ship.
>>>
>>> [AF] [...] but people are reluctant in using them on Macintoshes because of
>>> that problem of slowness.
>>>
>>> [JHS] If you're interested in working on the replacement, I can point you
>>> in the right direction. It's maybe 60% done ... all by a group of college
>>> seniors at PSU.
>>>
>>> --Jeremy
>>
>>
>> Alain
>>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> X11-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden