The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: David Arnold <davida@pobox.com>
To: Will Senn <will.senn@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Early GUI on Linux
Date: Tue, 28 Feb 2023 09:31:21 +1100	[thread overview]
Message-ID: <A2849A0E-61F4-4E24-BFAA-162F3653AE40@pobox.com> (raw)
In-Reply-To: <808dd3e1-3706-18d7-8109-4271a328d1c0@gmail.com>

I think this has its roots in the goals for the system.

Linux was developed (let’s say, in the pre 2.x era) as a way to make the PCs that many people could afford into the workstation they couldn't.

There was very little effort to make Linux a better operating system, let alone a better Unix: it was “is it good enough to do what I can/could do on Solaris at work/college?”

And so, it moved through a pragmatic subset of V7/Minix to a rough POSIX/Solaris syscall interface, and grew an ecosystem of cobbled-together userland that enabled that goal.  For the vast majority of its users, X11 was a pre-requisite for serious use: there was more-or-less zero impetus for a competing UI.  Perhaps the closest thing to it was GNUstep, which to this day, limps along with very little use (and is implemented over X11 anyway).

Look at how drawn-out the adoption of Wayland has been as evidence of how little interest there has been in alternative graphical models.

None of that is a bad thing, per se — give me Ubuntu 23.04 over Solaris 2.4 (or even 11) any day: mostly libre, mostly gratis, cheap hardware, and it just works.



d

> On 28 Feb 2023, at 07:56, Will Senn <will.senn@gmail.com> wrote:
> 
> Paul,
> While the background information on X alternatives is interesting, I think there's some conflation going on. The distance in time between the linux kernel being posted and X being available on it was an eyeblink, even back then. There was no serious effort to look at other windowing systems in between "hey, what do y'all think of my new kernel - it runs gnu stuff" to "here it is with X and X apps".
> 
> That said, it was a pain to configure, required just the right mix of video hardware and other hardware, and wasn't for the faint of heart. As X was becoming available on linux licketysplit, some folks either couldn't get it running or didn't have the hardware - those folks were probably the first to go looking at alternatives, but that didn't precede the x on linux effort.
> 
> Will
> 
> On 2/25/23 3:31 PM, Paul Ruizendaal wrote:
>> I think discussion of early Linux is in scope for this list, after all that is 30 years ago. Warren, if that is a mis-assumption please slap my wrist.
>> 
>> Following on from the recent discussion of early workstations and windowing systems, I’m wondering about early windowing on Linux. I only discovered Linux in the later nineties (Red Hat 4.x I think), and by that time Linux already seemed to have settled on Xfree86. At that time svgalib was still around but already abandoned.
>> 
>> By 1993 even student class PC hardware already outperformed the workstations of the early/mid eighties, memory was much more abundant and pixels were no longer bits but bytes (making drawing easier). Also, early Linux was (I think) more local machine oriented, not LAN oriented. Maybe a different system than X would have made sense.
>> 
>> In short, I could imagine a frame buffer device and a compositor for top-level windows (a trail that had been pioneered by Oriel half a decade before), a declarative widget set inspired by the contemporary early browsers and the earlier NeWS, etc. Yet nothing like that happened as far as I know. I vaguely recall an OS from the late 90’s that mixed Linux with a partly in-kernel GUI called “Berlin” or something like that, but I cannot find any trace of that today, so maybe I misremember.
>> 
>> So here are a few things that I am interested in and folks on this list might remember:
>> 
>> - were there any window systems popular on early Linux other than X?
>> 
>> - was there any discussion of alternatives to X?
>> 
>> - was there any discussion of what kernel support for graphics was appropriate?
>> 
>> 
> 


      parent reply	other threads:[~2023-02-27 22:31 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-25 21:31 [TUHS] " Paul Ruizendaal
2023-02-25 22:49 ` [TUHS] " Dan Cross
2023-02-26  1:27   ` Larry McVoy
2023-02-26  0:39 ` Warner Losh
2023-02-26  1:14   ` Steffen Nurpmeso
2023-02-26 15:50   ` Leah Neukirchen
2023-02-26 16:13     ` Larry McVoy
2023-02-26 16:23       ` Leah Neukirchen
2023-02-26 16:32         ` Warner Losh
2023-02-26 16:39         ` Will Senn
2023-02-26 19:58       ` Dave Horsfall
2023-02-27  0:16         ` Adam Thornton
2023-02-27 10:09       ` Ralph Corderoy
2023-02-26  2:21 ` Jonathan Gray
2023-02-27 17:22   ` Paul Ruizendaal
2023-02-27 18:32     ` Warner Losh
2023-02-26  2:27 ` Will Senn
2023-02-26  2:30 ` Will Senn
2023-02-26  2:40 ` Theodore Ts'o
2023-02-26  3:28   ` Dan Cross
2023-02-26  3:45     ` Warner Losh
2023-02-26  5:24   ` John Cowan
2023-02-26  5:36     ` Steve Nickolas
2023-02-28  3:35     ` Dave Horsfall
2023-02-27 17:22   ` Paul Ruizendaal via TUHS
2023-02-27 17:59     ` Arno Griffioen via TUHS
2023-02-27 18:07     ` Warner Losh
2023-02-27 20:04     ` [TUHS] Generational development [was Re: Re: Early GUI on Linux] arnold
2023-02-27 20:08       ` [TUHS] " Chet Ramey
2023-02-27 20:22         ` arnold
2023-02-27 20:46           ` segaloco via TUHS
2023-02-27 21:04             ` Dan Cross
2023-02-28  7:59             ` arnold
2023-02-28 15:28               ` Clem Cole
     [not found]                 ` <CAP2nic1STmWn5YTrnvFbexwwfYWT=pD28gXpVS1CVSfOOwxx7g@mail.gmail.com>
2023-02-28 15:50                   ` [TUHS] Fwd: " Adam Thornton
2023-02-27 20:50           ` [TUHS] " Chet Ramey
2023-02-27 20:55             ` Bakul Shah
2023-02-27 21:01               ` segaloco via TUHS
2023-02-27 21:15                 ` Chet Ramey
2023-02-27 21:22                   ` Dan Cross
2023-02-27 20:30     ` [TUHS] Re: Early GUI on Linux Dan Cross
2023-02-28  1:10       ` Alexis
2023-02-28  1:27         ` Dan Cross
2023-03-01 16:39       ` Paul Ruizendaal
2023-03-01 16:54         ` Larry McVoy
2023-03-01 17:22           ` Paul Ruizendaal
2023-03-01 17:52             ` Larry McVoy
2023-03-02  1:17               ` Jonathan Gray
2023-03-02  4:28               ` Larry McVoy
2023-03-02  6:46                 ` [TUHS] X timeline Lars Brinkhoff
2023-03-01 18:59         ` [TUHS] Re: Early GUI on Linux Theodore Ts'o
2023-03-02  7:27         ` arnold
2023-02-28  1:08     ` Jonathan Gray
2023-02-28  1:15       ` Clem Cole
2023-02-27 20:56 ` Will Senn
2023-02-27 22:14   ` Andru Luvisi
2023-02-27 22:31   ` David Arnold [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=A2849A0E-61F4-4E24-BFAA-162F3653AE40@pobox.com \
    --to=davida@pobox.com \
    --cc=tuhs@tuhs.org \
    --cc=will.senn@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).