NTPsec's longer-term objectives

[Mark Atwood]

Go has a GC. the Go standard library and the complier implementation will
always be utterly controlled by Google, and will be full of Google magic.
Go's usecase is to solve Google's problems, and can basically be modelled
as "compiled Python that forcefully avoids all of the kinds of typos that
Dr Pike got annoyed with typing for the past 30 years". It may make sense
to rewrite reposurgeon in Go, to break out of Python's performance
bottlenecks.

Rust is "C with sane types and sane scoping and sane string handling and
sane threading, with a focus on zero runtime cost abstractions".  If
someone was to write security critical internet facing daemons from
scratch, Rust would probably be the right choice.

..m

On Tue, Sep 13, 2016 at 12:35 AM Sanjeev Gupta <ghane0 at gmail.com> wrote:

>

>
> On Mon, Sep 12, 2016 at 8:14 PM, Eric S. Raymond <esr at thyrsus.com> wrote:

>>

>> While this is in some ways a tempting thought, I think the energy we
>> might spend on this would be better directed towards a newer language
>> that *is* suitable for soft realtime and has good provability properties
>> for security.  Rust or Go seem like the obvious candidates.
>
>
> /me rushes to reserve the GoNTPGo.com domain name.
>
> Now to squat till Mark and pals make me an offer.
>
> --
> Sanjeev Gupta
> +65 98551208     http://www.linkedin.com/in/ghane
> _______________________________________________
> devel mailing list
> devel at ntpsec.org <devel at ntpsec.org>
> http://lists.ntpsec.org/mailman/listinfo/devel
<http://lists.ntpsec.org/mailman/listinfo/devel>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/devel/attachments/20160914/b8e5bd63/attachment.html>