From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bakul Shah <bakul@bitblocks.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Thu,  2 May 2019 19:06:38 -0700
References: <CAO41-mOtG_2P1RgSb9gK2K83hTcEFf_qAqf8u+pidtm+rdBKNw@mail.gmail.com>
	<CAJSxfmJGk3CKes24U8Wtq2ENaabYWWhdVV=BHm2eAfk2Yi0FoA@mail.gmail.com>
	<CAFSF3XOSkq9RPz4wmo-+ipfRG270OEvfH5NBcvSxOGqjbXeZ-Q@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-Reply-To: <CAFSF3XOSkq9RPz4wmo-+ipfRG270OEvfH5NBcvSxOGqjbXeZ-Q@mail.gmail.com>
Message-Id: <099FC28B-3D5E-4D20-B7C0-542A14053F45@bitblocks.com>
Subject: Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
Topicbox-Message-UUID: fe7c3bbc-ead9-11e9-9d60-3106f5b1d025

On May 2, 2019, at 4:10 AM, hiro <23hiro@gmail.com> wrote:
>
>> Broadly speaking, that's [rio running inside rio] the essence of Rio.
>
> i have lately investigated the code of rio, devdraw and memlayer and
> understood a bit the historic connection to bitblt, etc., and i've
> been wondering lately where statements like above, which i have heard
> before, come from.
>
> they makes no sense to me, that rio nesting feature seems like an
> afterthought and involves a lot of back and forth which isn't just
> inefficient, but extremely inflexible!

Look at the moon, not the pointing finger.

[Answer kept below Skip's Twitter read limit.]