For a full-featured SSH running on a machine I was likely to log into and work interactively on, I'd prefer OpenSSH.
But most of what people do with SSH in a devops context isn't interactive; it's a simple control channel for well-defined sequences of file transfers and commands.
I'd prefer a minimal, Go/Rust-based SSH server for my EC2 servers, for instance.
I don't know why I'd prefer OpenNTP to a Go/Rust NTP. What's the advantage to it? OpenNTP is carefully built to avoid a class of bugs that its implementation language is very susceptible to. Go/Rust simply don't have those bugs at all. The latter seems like the safer option.
Same goes for DNS.
Re:GoBGP: BGP Implemented in Go
by nickpsecurity on Monday April 18, 2016 @03:02PM
(#11522315)
You can always do it close to original implementation. A straight-up clone. Should preserve at least most of the logical-level countermeasures.
(In particular, note that SSH daemons can fail in many ways other than by remote code execution.)
In the long run, C's role is indeed shrinking - but let's not be too hasty.