From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
Date: Fri, 3 May 2019 19:08:19 -0400 [thread overview]
Message-ID: <2abe5588-f865-42c9-89a4-92686d5bbb64@www.fastmail.com> (raw)
In-Reply-To: <CAFSF3XMeRYXXRc_80d8Qw8nuyC=y0RQiy3_935smi7b8n54E=g@mail.gmail.com>
On Fri, May 3, 2019, at 1:34 PM, hiro wrote:
> a lot of us younger people have an intuitive understanding only of
> newer hardware, and no idea about older bottlenecks, obvious back
> then.
Meanwhile, I have an intuitive understanding of older hardware and no idea about newer bottlenecks. And I'm starting to develop an OS. Great. Planning is going insanely well; today I thought I could get the filesystem to 'fall out of' variable allocation. (There was a bit more to it than that. ;)
I can't really help with your actual question, hiro, other than to say, "gotta go fast." Compression is one thing I've never really looked into beyond RLE.
On the actual thread topic, I guess Wio is cool. If it works as well as I think it does, I shall have to improve my opinion of Wayland.
Stray thought: Why didn't the suckless folk ever use Xnest instead of mucking about with things which require application support? Not that Xnest has worked 100% for years, but they could have tried to fix it. I mentioned it to them but they were already hyped up about tabbed.
next prev parent reply other threads:[~2019-05-03 23:08 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 4:12 Ryan Gonzalez
2019-05-02 4:17 ` Rodrigo G. López
2019-05-02 4:36 ` Skip Tavakkolian
2019-05-02 4:56 ` David Arnold
2019-05-02 7:13 ` Fazlul Shahriar
2019-05-02 11:15 ` hiro
2019-05-02 11:10 ` hiro
2019-05-02 14:07 ` hiro
2019-05-03 0:47 ` Skip Tavakkolian
2019-05-03 1:27 ` Dan Cross
2019-05-03 7:59 ` hiro
2019-05-03 8:20 ` hiro
2019-05-03 11:52 ` Lucio De Re
2019-05-03 12:32 ` hiro
2019-05-03 12:35 ` hiro
2019-05-03 17:01 ` Lucio De Re
2019-05-04 20:53 ` hiro
2019-05-05 3:19 ` Lucio De Re
2019-05-05 7:51 ` hiro
2019-05-05 8:34 ` Lucio De Re
2019-05-03 23:08 ` Ethan Gardener [this message]
2019-05-04 5:55 ` Jens Staal
2019-05-04 7:04 ` hiro
2019-05-07 3:48 ` 岡本健二
2019-05-03 2:06 ` Bakul Shah
2019-05-04 22:47 umbraticus
2019-05-05 7:53 ` hiro
2019-05-05 9:33 ` Lucio De Re
2019-05-05 10:01 ` hiro
2019-05-05 10:15 ` Lucio De Re
2019-05-05 11:09 ` hiro
2019-05-04 22:53 umbraticus
2019-05-05 12:32 cinap_lenrek
2019-05-05 13:50 ` Jens Staal
2019-05-05 17:16 ` hiro
2019-05-05 13:53 ` Lucio De Re
2019-05-05 15:14 ` Lucio De Re
2019-05-07 4:15 ` Lucio De Re
2019-05-08 12:32 ` Ethan Gardener
2019-05-09 7:39 ` Lucio De Re
2019-05-09 9:37 ` hiro
2019-05-05 14:14 cinap_lenrek
2019-05-05 15:59 ` Jens Staal
2019-05-05 15:11 cinap_lenrek
2019-05-05 15:22 cinap_lenrek
2019-05-05 15:32 ` Lucio De Re
2019-05-07 5:40 cinap_lenrek
2019-05-07 14:15 ` Lucio De Re
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=2abe5588-f865-42c9-89a4-92686d5bbb64@www.fastmail.com \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
/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).