Message-ID: <66a81d1f@news.ausics.net>
From: not@telling.you.invalid (Computer Nerd Kev)
Subject: Re: X Window System boot stipple
Newsgroups: comp.misc
References: <6691a266$2$1439836$882e4bbb@reader.netnews.com> <5FudnS1LIdXXJjv7nZ2dnZfqn_SdnZ2d@brightview.co.uk> <v88dkg$hkg7$1@dont-email.me>
User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (Linux/2.4.31 (i586))
NNTP-Posting-Host: news.ausics.net
Date: 30 Jul 2024 08:52:15 +1000
Organization: Ausics - https://newsgroups.ausics.net
Lines: 28
X-Complaints: abuse@ausics.net
Path: ...!weretis.net!feeder9.news.weretis.net!news.bbs.nz!news.ausics.net!not-for-mail
Bytes: 1804

John McCue <jmccue@magnetar.jmcunx.com> wrote:
> 
> Right now, I am hoping the BSDs would get together to keep
> X current, but I kind of doubt that will happen.

What's "current"? The biggest issue would be changes to the
operating systems that break old X code, and then obviously that
will be easy for the BSDs to fix/avoid because they're the ones
making the changes.

The other would be compiler changes breaking builds, but again such
people working on other big projects shouldn't struggle to tackle
that.

There's also graphics drivers, but then the X developers didn't
have the muscle to keep up with them on their own before anyway,
hence the widespread use of proprietary Nvidia drivers. Personally
my modest graphics needs are served by the VESA or framebuffer
drivers (I'm not sure if the latter exists on BSD), so I don't
really care whether X is "current" driver-wise.

Perhaps long-term the issue might be whether it's ported to new CPU
architectures like RISCV? That's a long way off though, there might
even be a replacement for Wayland by then.

-- 
__          __
#_ < |\| |< _#