I think a big reason a paper on replay can now get accepted is that rr got accepted first.
-
-
Replying to @samth @rocallahan
Something similar happened with Rust. The reviews of any Rust paper submissions were scathing right up until Rust got popular and everyone wanted in. Left me with a bad impression of academia, honestly.
3 replies 1 retweet 25 likes -
it's a common pattern in academia to be sure. it can be overcome, sometimes, by doing a really good job setting up the motivation, etc.
1 reply 0 retweets 5 likes -
Replying to @johnregehr @pcwalton and
academics are fundamentally extremely conservative, and any work that doesn't fit the current party line faces a major uphill battle to get accepted
2 replies 4 retweets 20 likes -
Replying to @johnregehr @pcwalton and
But the borrow checker, if nothing else, is a huge advance? Surely that should break through? He said, naively
1 reply 0 retweets 2 likes -
Replying to @fugueish @johnregehr and
It was seen as too similar to existing work
2 replies 0 retweets 5 likes -
I think the Rust pitch is made more complicated by Rust's lack of ambition relative to prior work. Rust basically says "don't try to make it possible to write a GC in fully safe code, instead make a usable language" but that's harder to describe.
2 replies 0 retweets 7 likes -
I would not characterize safe manual memory management as lack of ambition -- this was, even early on, obviously a major advance
3 replies 0 retweets 13 likes -
Replying to @johnregehr @samth and
There's a bunch of work on linear logic and affine typing that Rust draws on, as you know. Wouldn’t it be reasonable to describe that as “safe manual memory management”?
1 reply 0 retweets 1 like -
Replying to @bahstgwamt @kragen and
Usually it does so in ways that don’t replace GC or aren’t really practical for large programs. e.g. in modern terminology you would describe ML Kit as only supporting “arenas” that are freed all in one go.
3 replies 0 retweets 1 like
If you think trees are hard to deal with in Rust, imagine trying to write them in a language where you can’t free individual nodes at all. :)
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.