3 ms·
> a rewrite for the sake of safety is not sufficient imo I would disagree; I think a rewrite for the sake of safety, especially when we are talking about a pie
by kelnos 4y ago
> a rewrite for the sake of safety is not sufficient imo
I would disagree; I think a rewrite for the sake of safety, especially when we are talking about a piece of server software that deals with untrusted clients, is often worth it.
Certainly it isn't always: rewriting huge, complex pieces of software for the sake of anything (including safety) may just not be justifiable. Like, sure, maybe the Linux kernel would benefit from a rewrite in Rust, but I don't think that would be a good idea.
NTP is a fairly small protocol, and at least the server portion -- where I'd be the most worried about memory safety issues -- can be implemented in Rust without too much difficulty. As I understand it, NTP clients can be a bit more complicated. But I still expect they're much less complicated than many other types of clients.
> Are they going to maintain that forever and push Linux distro and the industry to move to that new solution?
Why not? That's how open source Linux software works. Someone builds it, and if there's enough interest, it gets adopted, and attracts new contributors and maintainers over time. If there isn't enough interest, it withers away.
That may not be your idea of the best use of your time (and I might agree), but who are we to tell others what to do with their time?