unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <ambrevar@gmail.com>
To: Tonton <tonton@riseup.net>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Code of Conduct and Diversity Statement
Date: Sun, 13 May 2018 10:08:03 +0200	[thread overview]
Message-ID: <87y3gokmfw.fsf@gmail.com> (raw)
In-Reply-To: <20180513022722.1b2349ef@merlin.browniehive.net>

[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]


From: https://www.recurse.com/blog/83-michael-nielsen-joins-the-recurse-center-to-help-build-a-research-lab

> To give some flavor for the types of work we’re excited by, here’s a
> small sampling of things that inspire us: [...] Systems Software
> Research is Irrelevant[1] [...]

I've read this paper (it's rather short) and as the title suggests, it
arguments over why there won't be anything new in research and that Unix
is "good enough".

This was 2000 and maybe there was nothing better, but in my opinion it
does not make those statements any less fallacious: Unix had issues
(people have written entire books[2] about it) and claiming to know to
where research is going to end is somewhat arrogant, isn't it?

And see, in 2008 Eelco Dolstra publishes the seminal paper "NixOS: A
Purely Functional Linux Distribution"[3], which proved Rob Pike awfully
wrong.

Anyways, saying all that because while Recurse looks great, it's sad
that their research initiative doesn't seem to believe in NixOS / GuixSD
:( Or did I get it wrong?

[1]: http://doc.cat-v.org/bell_labs/utah2000/utah2000.html

[2]: http://web.mit.edu/%7Esimsong/www/ugh.pdf

[3]: https://nixos.org/~eelco/pubs/nixos-icfp2008-final.pdf

--
Pierre Neidhardt

What one fool can do, another can.
		-- Ancient Simian Proverb

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      parent reply	other threads:[~2018-05-13  8:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13  0:27 Code of Conduct and Diversity Statement Tonton
2018-05-13  3:37 ` Chris Marusich
2018-05-13 12:47   ` Resources around inclusion, diversity, conduct and harrasment (was Re: Code of Conduct and Diversity Statement) Tonton
2018-05-13 21:50   ` Code of Conduct and Diversity Statement Ludovic Courtès
2018-05-14  0:21     ` Kei Kebreau
2018-05-14  8:25     ` Clément Lassieur
2018-05-17  6:26   ` Chris Marusich
2018-05-24 16:31     ` Leo Famulari
2018-05-24 17:13       ` Tobias Geerinckx-Rice
2018-05-29 16:32         ` Ludovic Courtès
2018-05-30  7:09           ` Ricardo Wurmus
2018-05-13  7:22 ` swedebugia
2018-05-13  7:35   ` Nils Gillmann
2018-05-13 20:29   ` Chris Marusich
2018-05-13  8:08 ` Pierre Neidhardt [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y3gokmfw.fsf@gmail.com \
    --to=ambrevar@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=tonton@riseup.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).