1 is more expensive than rewriting (presumably in Rust?), but it's not the same thing as rewriting in Rust, it gives you more.
-
-
Replying to @volatile_void @ManishEarth
2 can have a price comparable to rewriting in Rust, depending on coding style and subtlety of verified code. Many trade-offs…
2 replies 0 retweets 0 likes -
Replying to @volatile_void @ManishEarth
friend void Retweeted Who ordered *that*?
In particular, it needn't imply writing tons of specifications. So I totally disagree with this tweet:https://twitter.com/ManishEarth/status/885184757633392640 …
friend void added,
2 replies 0 retweets 0 likes -
Replying to @volatile_void @ManishEarth
On the other side, what's a good project to show that rewriting in Rust is feasible? https://github.com/briansmith/ring ? Last time I checks Ring still
2 replies 0 retweets 0 likes -
Replying to @volatile_void @ManishEarth
used some C functions. Unless there are better data points than Ring, I have to conclude that rewriting in Rust is expensive too.
1 reply 0 retweets 0 likes -
Replying to @volatile_void
No, the intent of Ring is to rewrite all the C in Rust except for the constant time crypto (which is asm+C).
2 replies 0 retweets 0 likes -
Replying to @ManishEarth
The goal with *ring* is to help other projects write Rust code by providing a reasonable Rust API. Not so much to implement *ring* in Rust.
1 reply 0 retweets 2 likes -
Replying to @BRIAN_____ @ManishEarth
The oxidation work we did does have some clear benefits, but also some of the projects using verified C w/ CompCert are very compelling.
1 reply 0 retweets 1 like -
Replying to @BRIAN_____ @ManishEarth
Also, many important rewrites don't look like rewrites. For example, in some sense Caddy is a rewrite of Apache in Go. Actually, it's more.
1 reply 0 retweets 1 like -
Replying to @BRIAN_____ @ManishEarth
We used BoringSSL's C code & gradually rewrote in Rust b/c I thought there'd be demand for TLS in Rust in 2015. Wrong. Maybe good marketing.
1 reply 0 retweets 2 likes
In retrospect, it would have been more efficient—higher throughput, higher latency—to take the asm code and start from scratch w/ the rest.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.