Why is this comment necessary? You don't have to read code or links if you don't want to. This is even worse than the "how is this topic relevant to hacker news" style comment.
I found it interesting because it is a nice example of real, non-toy, code in rust. I presume others find it interesting because it is a good progress mark of rust.
It is actually a pretty neutral and dry comment, which is not necessary a "jackassness".
Also, this is not a one-to-one conversation, other people read these threads as well. So some of them, which are genuinely interested, could benefit from detailed answers.
>It is actually a pretty neutral and dry comment, which is not necessary a "jackassness".
Not really convinced. Even something like "In what ways is this interesting? Can you explain?" would be way more neutral than the current one.
If he was perplexed by something on the article he would ask more specific questions.
As it stands, it's identical to tons of other dismissive comments that follow every announcement. It wants to imply the author is "too technical" for this, e.g "hmm, a yet another 3D engine just done on some new language this time? who cares" or "why is this on top of HN".
I found it interesting because it is a nice example of real, non-toy, code in rust. I presume others find it interesting because it is a good progress mark of rust.