Re: Future Direction of GNU Hurd?

"Jonathan S. Shapiro" <[email protected]> Tue, 15 Sep 2020 10:03:33 -0700
Newsgroups gmane.os.hurd.l4
Message-ID <CAAP=3QNj2oGTiLsoeFAxNnsNwhi=F_sYGPw55tt2FRDC=HENYw@mail.gmail.com>
--0000000000003a9e6b05af5d221b
Content-Type: text/plain; charset="UTF-8"

Valerio:

Thank you for your kind words regarding Coyotos. Looking back -- and
looking now from a perspective that is now several years removed -- I feel
that I wouldn't approach matters that way today. Other technologies have
moved forward in ways that could achieve many of the high-level Coyotos
goals more quickly and more cost-effectively. The goal was to move several
"balls" forward; I was never foolish enough to imagine replacing the
entirety of existing infrastructure.

It's a write-up I should do, but the l4-hurd list doesn't seem like an
appropriate place to do it.


Jonathan

--0000000000003a9e6b05af5d221b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Valerio:</div><div dir=3D"ltr"><br></div>=
<div dir=3D"ltr">Thank you for your kind words regarding Coyotos. Looking b=
ack -- and looking now from a perspective that is now several years removed=
 -- I feel that I wouldn&#39;t approach matters that way today. Other techn=
ologies have moved forward in ways that could achieve many of the high-leve=
l Coyotos goals more quickly and more cost-effectively. The goal was to mov=
e several &quot;balls&quot; forward; I was never foolish enough to imagine =
replacing the entirety of existing infrastructure.<br></div><div dir=3D"ltr=
"><br></div><div>It&#39;s a write-up I should do, but the l4-hurd list does=
n&#39;t seem like an appropriate place to do it.</div><div><br></div><div><=
br></div><div>Jonathan</div><div><br></div></div>

--0000000000003a9e6b05af5d221b--