From: Ethan Gardener <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] !#&%&^#*@ RIO!!!
Date: Thu, 13 Dec 2018 13:28:11 +0000 [thread overview]
Message-ID: <1544707691.1511402.1608097856.46B20629@webmail.messagingengine.com> (raw)
In-Reply-To: <26B6FB24FAC120B8B424D0C3246CF039@felloff.net>
On Thu, Dec 13, 2018, at 11:23 AM, cinap_lenrek@felloff.net wrote:
> huh? rio doesnt use event library.
i know.
> it uses mouse(2) instead, which gives
> you a Mousectl* that contains a channel. the "mouse" variable of
> type Mouse* points into that mousectl
^-- This part is completely invisible in the code. That's my complaint.
It might not be so bad if I lived and breathed Plan 9, I suppose,
but I don't want to go that far. Without that level of familiarity,
the code is as clear as mud.
I suppose I'm complaining about a convenience feature making it
unclear, but I just got badly stressed over it *again*. It turns out
it's not even rio, but a library feature rio makes heavy use of.
It's certainly made me rethink my opinion of convenience features.
If the library didn't provide this, the code which uses it would have
an indication of where the data is coming from.
Even if rio assigned the "mouse" variable in exactly the way the
library presently does, I wouldn't have got stressed trying to find it.
Thank you for your clear explanation, but I don't think I'll pursue
this further with these libraries. Various things from /sys/src/libdraw
have caused me stress, so I've put new libraries on my hobby list. :)
Maybe I'll get them done, or maybe I'll give up on programming
anything of any depth. I don't know.
next prev parent reply other threads:[~2018-12-13 13:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 11:23 cinap_lenrek
2018-12-13 13:28 ` Ethan Gardener [this message]
2018-12-18 22:47 ` Reading/understanding OS code (WAS: Re: [9front] !#&%&^#*@ RIO!!!) magma698hfsp273p9f
2018-12-18 23:41 ` Julius Schmidt
2018-12-19 7:44 ` Steve Simon
2018-12-19 8:19 ` hiro
2018-12-19 8:02 ` hiro
2018-12-20 20:20 ` Ethan Gardener
2018-12-20 20:12 ` Ethan Gardener
2018-12-21 8:22 ` Reading/understanding OS code -- documentation Ethan Gardener
2018-12-13 13:44 [9front] !#&%&^#*@ RIO!!! cinap_lenrek
2018-12-13 21:13 ` Ethan Gardener
2018-12-14 11:22 ` Ethan Gardener
2018-12-14 11:46 ` hiro
2018-12-14 13:23 ` Ethan Gardener
2018-12-14 14:16 ` hiro
2018-12-14 15:04 ` Stanley Lieber
2018-12-14 23:46 ` Steve Simon
2018-12-15 13:41 ` Ethan Gardener
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=1544707691.1511402.1608097856.46B20629@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--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).