9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] Getting git9 -- moved to github.
Date: Mon, 3 Feb 2020 21:42:34 +0100	[thread overview]
Message-ID: <4ED728FD208A918FB3344EF919BEE6E8@felloff.net> (raw)
In-Reply-To: <CAJQ9t7h=f6-9Oz=NOTrVk6ONWKNBM6TmDODCCnvHJG0MmYRBbw@mail.gmail.com>

> But where I only partially agree is where Plan 9 concepts contradict
> what may be "common practice". A URL is a well defined object and
> adopting it as a standard, as quite a few services have done (I'm
> thinking PostgreSQL and OpenLDAP, for example) rather than pursue the
> '!' convention seems worth it.

i find plan9 dialstrings much easier to deal with than urls
that have all kinds of escapes and encodings depending on
which part in the url stuff appears in. they carry alot of
baggage arround.

urls might appear in ASCII context, then you need to punicode
the domain name if it happens to contain non-ascii characters
while plan9 dial strings are guaranteed to work consistently.
the resolution process is done by ndb/cs and it can accept
unicode just fine.

plus picking the "!" as a separator works with ipv6 while
using ":" needs v6 literal escapes like:

[2001:1:2:3:4::]:22

this was a huge mistake. in plan9 we are lucky not to
be affected by this too much and we can handle these
things without much pain and without touching every
program.

dialstrings also let you pick the protocol and also the
ip stack to use. programs that do not accept dialstrings
sabotage a usefull plan9 capability and break consistency.

i'm pretty sure the original plan9 ssh1/ssh2 also accept
dial strings just fine.

thats just like, my opinion, man.

--
cinap

  parent reply	other threads:[~2020-02-03 20:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19 17:03 ori
2020-01-27 21:23 ` [9fans] " Sergey Zhilkin
2020-02-02  9:58 ` Lucio De Re
2020-02-02 10:35   ` kvik
2020-02-02 14:39     ` Lucio De Re
2020-02-02 22:47       ` hiro
2020-02-02 23:28         ` cinap_lenrek
2020-02-03  0:55   ` ori
2020-02-03  0:57   ` ori
2020-02-03  4:07     ` Lucio De Re
2020-02-03  4:11       ` ori
2020-02-03  7:39         ` Lucio De Re
2020-02-03 10:01           ` hiro
2020-02-03 11:10             ` Lucio De Re
2020-02-03 13:54               ` hiro
2020-02-03 14:40                 ` Lucio De Re
2020-02-03 16:14                   ` ori
2020-02-04  4:07                     ` Lucio De Re
2020-06-20 15:58                       ` Lucio De Re
2020-02-03 20:42                   ` cinap_lenrek [this message]
2020-02-04  4:03                     ` 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=4ED728FD208A918FB3344EF919BEE6E8@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --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).