5 ms·

What would be the proper way of informing those who are interested in the topic about available alternatives? I assume not everyone follows the same topics and

What would be the proper way of informing those who are interested in the topic about available alternatives? I assume not everyone follows the same topics and there may be people who see the presented information and the relevant references for the first time.

pvg 6y ago
You know the sort of person who comments 'Just install Linux' in every thread about more or less any kind of computer problem? You don't want to be that sort of person. If you're starting your comments with 'I'm not going to stop telling you to install Linux', it's probably a good time to check if you're not turning into the sort of person who's always telling you to install Linux.
- ghostwriter 6y ago
  If I ommited that first part of the sentence the points made afterwards would remain the same. I did so to indicate that it's not the first time the Rust community suggests that something should be (re-)written in Rust for memory-safety reasons, in a project that has a well-established C-codebase. I'd argue it's the same "Just install Linux" situation that you mention, and that "Linux" may not be the answer.
  - pvg 6y ago
    it's not the first time the Rust community suggests that something should be (re-)written in Rust The article is not about that, though, it's specifically about the various issues surrounding the use of Rust for Linux kernel development.
  - Ar-Curunir 6y ago
    The Rust community is not advocating that, it’s kernel developers that are interested in writing new components in Rust. So no proposal of rewriting by any Rust developers
    - geofft 6y ago
      And 'ghostwriter stated elsewhere in this thread that the previous round of these comments was in reply to an article talking about how QEMU should start to develop new device backends as out-of-process Rust programs - which also was not about outsiders proposing a complete rewrite, either. https://news.ycombinator.com/item?id=24133292 https://news.ycombinator.com/item?id=24133292 http://blog.vmsplice.net/2020/08/why-qemu-should-move-from-c-to-rust.html http://blog.vmsplice.net/2020/08/why-qemu-should-move-from-c... Perhaps the most long-lasting harm of the Rust Evangelism Strike Force has been the rise of the Anything But Rust Counterinsurgency, who sees that someone, somewhere, is thinking about Rust, and needs to convince them that they're making a mistake.
billziss 6y ago
I, for one, am glad that you chose to comment as I had never heard of ATS before. Thank you.
geofft 6y ago
At the very least, please include links to your previous comments, so that any refutations of your previous comments can be seen by others - otherwise we will all have to repeat ourselves until there is no room for any new discussion. (One of the other replies pointed out that you had not incorporated an objection that someone made to your previous comment.)
dang 6y ago
I think if you absorb the responses from other users here, and adapt your future comments more to the specifics of a given story, that should help a lot. geofft makes a good point about linking to past points rather than repeating them. That's the way to handle repetition on HN. Don't inline generic material from before—refer to it via links.

pvg 6y ago

You know the sort of person who comments 'Just install Linux' in every thread about more or less any kind of computer problem? You don't want to be that sort of person. If you're starting your comments with 'I'm not going to stop telling you to install Linux', it's probably a good time to check if you're not turning into the sort of person who's always telling you to install Linux.

ghostwriter 6y ago
If I ommited that first part of the sentence the points made afterwards would remain the same. I did so to indicate that it's not the first time the Rust community suggests that something should be (re-)written in Rust for memory-safety reasons, in a project that has a well-established C-codebase. I'd argue it's the same "Just install Linux" situation that you mention, and that "Linux" may not be the answer.
- pvg 6y ago
  it's not the first time the Rust community suggests that something should be (re-)written in Rust The article is not about that, though, it's specifically about the various issues surrounding the use of Rust for Linux kernel development.
- Ar-Curunir 6y ago
  The Rust community is not advocating that, it’s kernel developers that are interested in writing new components in Rust. So no proposal of rewriting by any Rust developers
  - geofft 6y ago
    And 'ghostwriter stated elsewhere in this thread that the previous round of these comments was in reply to an article talking about how QEMU should start to develop new device backends as out-of-process Rust programs - which also was not about outsiders proposing a complete rewrite, either. https://news.ycombinator.com/item?id=24133292 https://news.ycombinator.com/item?id=24133292 http://blog.vmsplice.net/2020/08/why-qemu-should-move-from-c-to-rust.html http://blog.vmsplice.net/2020/08/why-qemu-should-move-from-c... Perhaps the most long-lasting harm of the Rust Evangelism Strike Force has been the rise of the Anything But Rust Counterinsurgency, who sees that someone, somewhere, is thinking about Rust, and needs to convince them that they're making a mistake.

billziss 6y ago

I, for one, am glad that you chose to comment as I had never heard of ATS before. Thank you.

geofft 6y ago

At the very least, please include links to your previous comments, so that any refutations of your previous comments can be seen by others - otherwise we will all have to repeat ourselves until there is no room for any new discussion. (One of the other replies pointed out that you had not incorporated an objection that someone made to your previous comment.)

dang 6y ago

I think if you absorb the responses from other users here, and adapt your future comments more to the specifics of a given story, that should help a lot. geofft makes a good point about linking to past points rather than repeating them. That's the way to handle repetition on HN. Don't inline generic material from before—refer to it via links.