9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio.dere@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] microsoft's plan 9 distribution
Date: Sat, 16 Feb 2019 12:34:25 +0200	[thread overview]
Message-ID: <CAJQ9t7gLnZDKcgJ26Qd2kRwqpWfyUXw_PaQJr-xaqn1FWPPxaQ@mail.gmail.com> (raw)
In-Reply-To: <CAJSxfmL+6Ccc52Q+TmjjmodJWVsU4SSLssSyz=dfzFxE=X8gMw@mail.gmail.com>

Hell, I wish I could figure out what I want!

I need to use Thunderbird as my mailer and that keeps reminding me how
liberating it was some long time back when I was able to move from
Mutt to Acme/Mail: the latter is so much less of a burden across so
many aspects. But today I'd have to change job to get rid of
Thunderbird and that's not going to happen.

Then, there's GIT. Another annoying must-have. I really have to look
into "gitfs" and dedicate daily time to create a Plan 9 compatible
(that means Go, in my life, incidentally) VCS that is not a
monstrosity. I doubt there's much hope to get that right.

To close, there's Chrome. I can't for the hell of me understand how no
one has declared the browser a health (mental and social) hazard. It's
worse than DDT, by far.

So, that's just a few places where I expect that a concerted effort
from a willing community could put Plan 9 to great use. But of course
contributions from bright minorities have been identified as contrary
to the interests of the powerful elites and the bar set far too high
to be overcome; specifically, not necessarily consciously, to prevent
disruptive technologies taking hold. I can't reconcile myself to the
idea that this may be for the best.

And then Microsoft comes along and hi-jacks just enough of my
favourite security blanket to make me feel discriminated against.

Lucio.



  reply	other threads:[~2019-02-16 10:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-16  0:48 hiro
2019-02-16  0:58 ` Kurt H Maier
2019-02-16  1:20   ` Skip Tavakkolian
2019-02-16  3:57   ` Lucio De Re
2019-02-16  8:53     ` Steve Simon
2019-02-16  9:30       ` Lucio De Re
2019-02-16 10:08       ` Skip Tavakkolian
2019-02-16 10:34         ` Lucio De Re [this message]
2019-02-16 12:50       ` Charles Forsyth
2019-03-07 10:07         ` Steve Simon
2019-02-16  9:35     ` hiro
2019-02-16 11:52       ` Lucio De Re
2019-02-16 15:38         ` hiro
2019-02-16  2:00 ` Jeremy O'Brien
2019-02-16 12:28 ` Charles Forsyth
2019-02-17 11:34 ` Ethan Gardener
2019-02-18  4:13   ` Lucio De Re
2019-02-18 21:02   ` Lyndon Nerenberg
2019-02-18 22:02     ` hiro
2019-02-20  8:52     ` Ethan Gardener
2019-02-20  9:13       ` Ethan Gardener
2019-02-20 21:36         ` hiro

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=CAJQ9t7gLnZDKcgJ26Qd2kRwqpWfyUXw_PaQJr-xaqn1FWPPxaQ@mail.gmail.com \
    --to=lucio.dere@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).