<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<div class="moz-cite-prefix">On 11/04/2017 07:59 PM, Eric S. Raymond
via devel wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20171104235923.09BB013A73D7@snark.thyrsus.com">
<pre wrap="">Here's my big question about the next year of development: should we
be moving the codebase out of C to Go?
I think the project is feasible and the potential gains are large, but
I don't want to start anything without being sure our senior devs are
happy with the idea. This means everybody's concerns need to be heard
well before any code is cut.
....
Thoughts?
</pre>
</blockquote>
<br>
<div class="moz-signature">Not to be the grognard here, but trying
to weigh in from the (theoretical) customers' perspective.<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<title></title>
<p>Since we're trying to get adoption by big-site sysadmins, who
are (or tend to be) a technically conservative bunch, I'm
concerned that they will see code in a "brand-new" language as
possibly too risky. (Yes, they nearly always install from
vendor- or distro-supplied packages, so binaries only. But the
implication of "you can always download and build your own from
source" means that the source language has _some_ weight in
their considerations.)</p>
<p>I think some serious prototyping needs to be done in Go, but
that, until we get significant uptake, the released versions
should be in a "tried and true" language (_even_ with the
security/reliability considerations.)</p>
<p><br>
</p>
<p>My $0.02 worth.<br>
</p>
<p><br>
</p>
<p> - <font color="#000099"><b><font face="Brush Script MT"
size="+3">John D. Bell</font></b></font></p>
</div>
</body>
</html>