9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] rio: resize border and scrollbar based on font
Date: Sat, 11 May 2024 18:54:53 +0200	[thread overview]
Message-ID: <CAFSF3XOZ0J8j6=UA_DkUKbg8SpuNtF0PRKW7Z91wrO0-38pUrg@mail.gmail.com> (raw)
In-Reply-To: <10658a6d-38bc-4b49-bc13-c42cc0113034@posixcafe.org>

i'm glad people are invested into the code they wrote, but as ori and
moody explained in depth doing a significant improvent to the current
lack of scaling would require huge amount of changes in many unrelated
components.

if you want to make it more probable that rio is ever replaced, I
think you should think of improving our overall graphics system. you
could work on this in parallel to all the current limited
rio/libdraw/devdraw graphical programs. i think it's not possible for
a single person to do though.

My reason is that rio sucks, and devdraw sucks, mainly bec. both
depend on each other in a clunky way. Given that this is already a
second-system I'm quite surprised how little apparent thought went
into this design. So yeah, I propose a third-system that takes a more
educated approach concentrating on actually making simple graphics/UI
abstractions, as opposed to making a demo/example/benchmark
application for concurrency and parallelism in an incomplete
multiprocessor system.
Just be careful with those overly abstract and generic graphics
toolkits, they are often way more complicated what would be needed to
replace rio/libdraw/devdraw.

  reply	other threads:[~2024-05-11 16:58 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10  6:13 Romano
2024-05-10 13:27 ` Kristo
2024-05-10 14:01   ` Stanley Lieber
2024-05-10 14:17 ` Jacob Moody
2024-05-10 18:43   ` Romano
2024-05-10 19:15     ` Jacob Moody
2024-05-10 19:40       ` ori
2024-05-11 16:45         ` hiro
2024-05-11  4:31       ` Romano
2024-05-11 15:00         ` Jacob Moody
2024-05-11 16:54           ` hiro [this message]
2024-05-13  5:18           ` Romano
2024-05-11 16:42       ` hiro
2024-05-10 21:00     ` sl
2024-05-11  4:34       ` Romano
2024-05-13  5:38         ` Romano
  -- strict thread matches above, loose matches on Subject: below --
2024-05-09 21:04 Romano
2024-05-10  0:14 ` Jacob Moody
2024-05-10  0:34   ` sl
2024-05-10  6:20   ` Kurt H Maier
2024-05-10 14:10     ` Jacob Moody
2024-05-10 14:16       ` Stanley Lieber
2024-05-10 14:20         ` Jacob Moody
2024-05-10 14:23           ` Stanley Lieber
2024-05-10 14:21         ` ori
2024-05-10 14:33           ` Stanley Lieber
2024-05-10 14:37             ` Stanley Lieber
2024-05-10 14:58       ` Kurt H Maier
2024-05-10 15:28         ` Stuart Morrow
2024-05-10 16:11           ` Stanley Lieber
2024-05-10 16:43             ` Stuart Morrow
2024-05-10 16:50               ` Stuart Morrow
2024-05-11 16:36               ` hiro
2024-05-11 16:30             ` hiro
2024-05-11 16:27       ` hiro
2024-05-11 16:36         ` Jacob Moody

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='CAFSF3XOZ0J8j6=UA_DkUKbg8SpuNtF0PRKW7Z91wrO0-38pUrg@mail.gmail.com' \
    --to=23hiro@gmail.com \
    --cc=9front@9front.org \
    /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).