From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] unix "awesome list"
Date: Tue, 8 May 2018 11:17:22 -0400 (EDT) [thread overview]
Message-ID: <20180508151722.49CFC18C079@mercury.lcs.mit.edu> (raw)
> From: Clem Cole
> I agree with Tannenbaum that uKernel's make more sense to me in the long
> run - even if they do cost something in speed
There's a certain irony in people complaining that ukernel's have more
overhead - while at the same time time mindlessly, and almost universally,
propogating such pinheaded computing hogs as '_mandating_ https for everything
under the sun' (even things as utterly pointless to protect as looking at
Wikipedia articles on mathematics), while simultaneously letting
Amazon/Facebook/Google do the 'all your data are belong to us' number; the
piling of Pelion upon Ossa in all the active content (page after page of
JavaScript, etc) in many (most?) modern Web sites that does nothing more than
'eye candy'; etc, etc.
Noel
next reply other threads:[~2018-05-08 15:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 15:17 Noel Chiappa [this message]
2018-05-08 15:22 ` Warner Losh
2018-05-08 16:18 ` Arthur Krewat
2018-05-08 19:37 ` Dave Horsfall
2018-05-08 19:54 ` Grant Taylor
-- strict thread matches above, loose matches on Subject: below --
2018-05-07 18:22 A. P. Garcia
2018-05-07 21:10 ` Dave Horsfall
2018-05-07 21:53 ` Steve Johnson
2018-05-08 12:24 ` Theodore Y. Ts'o
2018-05-08 13:51 ` Bakul Shah
2018-05-08 14:53 ` Clem Cole
2018-05-08 15:23 ` Jon Steinhart
2018-05-08 15:31 ` Steve Johnson
2018-05-08 16:32 ` Clem Cole
2018-05-08 17:33 ` Theodore Y. Ts'o
2018-05-08 18:40 ` William Cheswick
2018-05-08 21:25 ` Bakul Shah
2018-05-08 21:15 ` Bakul Shah
2018-05-08 16:31 ` Michael Parson
2018-05-08 17:20 ` Larry McVoy
2018-05-08 17:49 ` Michael Parson
2018-05-08 20:48 ` Dave Horsfall
2018-05-08 17:53 ` Theodore Y. Ts'o
2018-05-07 21:54 ` Steve Nickolas
2018-05-08 8:14 ` Mutiny
2018-05-07 22:34 ` Andy Kosela
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=20180508151722.49CFC18C079@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
/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).