Richard Laager said:
> With the caveat that there is a LOT I don't know in this space, if it was my
> call, I'd aim for an incremental conversion of ntpd to Rust and leave the
> userspace tooling in Python. After the daemon is converted, I would
> re-evaluate whether the userspace tooling
On 6/20/21 4:45 PM, Richard Laager via devel wrote:
I get the impression that Go has a shallower learning curve (i.e. is
easier to get started with), which is good, but may unfairly prejudice
Go in quick Go-vs-Rust "bake off" comparisons.
err... may unfairly prejudice Rust
--
Richard
On 6/20/21 2:31 AM, Achim Gratz via devel wrote:
Eric S. Raymond via devel writes:
My choice for a language to move to would be Go. Possibly one of you
can argue for a different choice, though if you agree that Go is a
suitable target I would find that information interesting.
Since the last
Hal Murray via devel writes:
> e...@thyrsus.com said:
>> I did. There's a blog post about it:
>> https://blog.ntpsec.org/2017/02/22/testframe-the-epic-failure.html
>
> From there:
>> One was what in discussion on the mailing list I later tagged "the code-path
>> split". There are two kinds of
MLewis via devel writes:
> Is it worthwhile improving the current C code to a 'hardened' programming
> standard?
It's always worth trying, but not as easy as it seems. The fun with
standard is that there are so many to chose from.
> Example
> - Joint Strike Fighter standards
Achim Gratz said:
> Since the last round of discussion both sides of the argument have been
> moving. If you believe that Rust will become a first-class implementation
> language for the Linux kernel, that would tip the scales in favor of rust
> considerably in my view.
Thanks.
I just
Eric S. Raymond via devel writes:
> My choice for a language to move to would be Go. Possibly one of you
> can argue for a different choice, though if you agree that Go is a
> suitable target I would find that information interesting.
Since the last round of discussion both sides of the argument
> 1. We have at least two people who are expert Go programmers - Ian and
> myself. We have nobody, AFAIK, who is up to speed on Rust. Moving
> the code will be a large amount of work - I don't think any good
> purpose is siolved by adding "learn to be fluent in an entire new
> language" on top
e...@thyrsus.com said:
> I did. There's a blog post about it:
> https://blog.ntpsec.org/2017/02/22/testframe-the-epic-failure.html
>From there:
> One was what in discussion on the mailing list I later tagged "the code-path
> split". There are two kinds of NTP hosts; one uses a kernel facility
MLewis :
>Is it worthwhile improving the current C code to a 'hardened' programming
>standard?�
>
>Example
>- Joint Strike Fighter standards
>[1]https://www.stroustrup.com/JSF-AV-rules.pdf
>- NASA JPL standards
>
>
James Browning via devel :
> Are there any C to golang or rust transpilers that work
> reasonably well? The last time I checked the best rust
> transpiler generated rs files that were just shallow glosses
> and the golang transpiler was somewhat inadequate and
> verbose.
This is still the state
Yo MLewis!
On Fri, 18 Jun 2021 20:17:56 -0400
MLewis via devel wrote:
> Is it worthwhile improving the current C code to a 'hardened'
> programming standard?�
>
> Example
> - Joint Strike Fighter standards
> https://www.stroustrup.com/JSF-AV-rules.pdf
That is for C++. And anything JSF
Hal Murray :
> What was the name for your attempt to get a GPSD style replay of old data?
> Did we ever figure out why that didn't work?
I did. There's a blog post about it:
https://blog.ntpsec.org/2017/02/22/testframe-the-epic-failure.html
--
http://www.catb.org/~esr/;>Eric
Hal Murray :
> > I'll start the ball rolling with this big one: It's time to move out of C.
>
> I want to threadify things, and taking advantage of that, I want to run at
> full wire speed on a gigabit link with a modest server class CPU.
>
> I have test code running. I'm pretty sure it will
Is it worthwhile improving the current C code to a 'hardened'
programming standard?�
Example
- Joint Strike Fighter standards
https://www.stroustrup.com/JSF-AV-rules.pdf
- NASA JPL standards
Are there any C to golang or rust transpilers that work
reasonably well? The last time I checked the best rust
transpiler generated rs files that were just shallow glosses
and the golang transpiler was somewhat inadequate and
verbose.
An early-started long-lived tread for each of DNS, clock-
On Fri, Jun 18, 2021, at 6:08 AM Hal Murray via devel wrote:
>
> As long as we are in blue sky mode...
>
> What was the name for your attempt to get a GPSD style replay of old data?
> Did we ever figure out why that didn't work?
It was called testframe IIRC...
As long as we are in blue sky mode...
What was the name for your attempt to get a GPSD style replay of old data?
Did we ever figure out why that didn't work?
The GPSD code is one way: Input => output. There is no back and forth, no
request => response which changes internal state. Does that
> I'll start the ball rolling with this big one: It's time to move out of C.
I want to threadify things, and taking advantage of that, I want to run at
full wire speed on a gigabit link with a modest server class CPU.
I have test code running. I'm pretty sure it will work. But my test code
Developers, please weigh in on what you think the NTPSec project's
goals for the next year ought to be. These goals can be coding
projects ("Move the Python code to Go") process goals ("Halve the size
of the issue list") or project infrastructure goals ("Build a hardware
lab so we can live-test
20 matches
Mail list logo
