From mboxrd@z Thu Jan 1 00:00:00 1970 User-Agent: Cyrus-JMAP/3.1.6-449-gfb3fc5a-fmstable-20190430v1 Mime-Version: 1.0 Message-Id: <2abe5588-f865-42c9-89a4-92686d5bbb64@www.fastmail.com> In-Reply-To: References: Date: Fri, 3 May 2019 19:08:19 -0400 From: "Ethan Gardener" To: 9fans@9fans.net Content-Type: text/plain Subject: Re: [9fans] Someone made a Wayland compositor based on Rio, Wio Topicbox-Message-UUID: fead53aa-ead9-11e9-9d60-3106f5b1d025 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.