From: dante <subscriptions@posteo.eu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] OT: What linux has become
Date: Wed, 13 Aug 2014 10:02:46 +0200 [thread overview]
Message-ID: <c1a0a8892d9778576d398301d5a32b7b@posteo.de> (raw)
In-Reply-To: <201408130453.s7D4rPGQ025252@skeeve.com>
This is a valid observation, although as everything that has to do with
architecture, hard to prove.
(Don't use the P-word, that's reserved for Plato and Nietzsche.)
I also have the impression that the trend set by the original Unix
architecture (small, one-job components, generic interfaces)
is nowadays replaced in many areas with integrated solutions
("frameworks") that provide non-separable components
and sometimes redundant interfaces.
For systemd, according to Wikipedia, it provides:
- socket *and* d-bus interfaces
- a cron-like scheduler
- a logging facility, but also access to syslogd
- udev, which was pretty complex itself (frustrating for me: useless
for my setup, had to learn it without having any curiosity/interest)
- etc.
WHY?
The trend can also be seen in other areas. Take Spring for Java:
gathers together components that were implemented
separately long time ago. Or even the iOS aps: there is no meaningful
IPC there.
One reason why I try to take what I can from Plan9 is that I profoundly
mistrust systems that I cannot understand due to their size/bloat.
Arnold, thanks for the food for the mind :-).
Cheers,
Dante
On 13.08.2014 06:53, Aharon Robbins wrote:
> http://lkml.iu.edu//hypermail/linux/kernel/1408.1/02496.html
>
> Someone should turn this guy on to Plan 9. :-)
>
> Arnold
next prev parent reply other threads:[~2014-08-13 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 4:53 Aharon Robbins
2014-08-13 5:41 ` Eris Discordia
2014-08-13 7:57 ` cam
2014-08-13 8:02 ` dante [this message]
2014-08-13 10:01 ` tlaronde
2014-08-13 10:11 ` hiro
2014-08-13 16:24 ` lucio
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=c1a0a8892d9778576d398301d5a32b7b@posteo.de \
--to=subscriptions@posteo.eu \
--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).