From: hiro <23hiro@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
Date: Fri, 3 May 2019 14:32:59 +0200 [thread overview]
Message-ID: <CAFSF3XMeRYXXRc_80d8Qw8nuyC=y0RQiy3_935smi7b8n54E=g@mail.gmail.com> (raw)
In-Reply-To: <CAJQ9t7jbwJ9dzrREHKn=yfGCszN-n6kcKpZjCAEVh4uKOGuudA@mail.gmail.com>
i think you mean the devdraw lempel-ziv compressed images. font images
are just images really (on the memlayer below devdraw), and i also
tried to understand the compression code (the first i ever looked at),
but couldn't.
they did recommend to read that original paper by lempel-ziv and i
didn't - probably i am at fault.
i agree there is inperfection. i find it entertaining to find the
historic reasons how it became like this, and having this excuse
doesn't lessen their work's quality.
i truly think there is some amazing stuff to learn from plan9 design,
but technologic change in the meantime makes a lot of these things
less obvious.
a lot of us younger people have an intuitive understanding only of
newer hardware, and no idea about older bottlenecks, obvious back
then. hence my asking here. trying to check my (i admit somewhat
phantastic) theories :)
> given that Plan 9 is so much simpler than the more popular OSes around, how is it that it does not outperform them?
it does here. disk access on linux is sooooo much higher latency
indeed. it's truly mind-boggling.
my suspicion is that this helps protect the linux disk performance
engineer jobs. we have met such a fellow once during some 9front
benchmarking next to the billiard table. he overheard our conversation
and wanted to offer his services. very nice guy even. probably best
for him that he doesn't know...
> why isn't there a Plan 9 tool that can beat Skype at at least the texting portion of its game
you HAVE to try the hubchat on mycroftiv's grid!
next prev parent reply other threads:[~2019-05-03 12:32 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 [this message]
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
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='CAFSF3XMeRYXXRc_80d8Qw8nuyC=y0RQiy3_935smi7b8n54E=g@mail.gmail.com' \
--to=23hiro@gmail.com \
--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).