3 ms·
That's what makes blog posts like this tricky: this post is one for the project itself, which means that its audience is already for people who know what the pr
by steveklabnik 10y ago
That's what makes blog posts like this tricky: this post is one for the project itself, which means that its audience is already for people who know what the project is, etc. Someone posted it on HN, and it got upvotes, so it gets to a broader audience, who may not inherently know these kinds of things, or not care.
So your point here is valid, that is, "as someone _not_ in that audience, why should I care?" That's what the other thread, with its replies, is getting at. Which is why I pointed to you to it.
It's possible as well, of course, that maybe that _still_ means this doesn't matter to you. Which is also expected; nobody is going to like every thread on HN. That's why the guidelines[1] have the section of "Please don't submit comments complaining that a submission is inappropriate for the site." And it gives you something to do instead: " If you think a story is spam or off-topic, flag it by clicking on its 'flag' link." And beyond that, you could just skip this thread and read any of the other 29 posts on the front page. That's how I usually handle posts that I don't have any particular interest in.
https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- lacampbell 10y agoConstructive criticism is nothing to shy away from or be defensive about. Having criticism for something doesn't mean I think it's spam or off topic. Again, for an example of a language X-to-language-Y rewrite story with some substance, that did a lot to boost the image of the language in many peoples eyes, see: http://roscidus.com/blog/blog/2014/06/06/python-to-ocaml-retrospective/ http://roscidus.com/blog/blog/2014/06/06/python-to-ocaml-ret... I'd love to something like that the next time "X rewritten in rust" etc gets to the front page of hacker news. A re-write in of itself tells me nothing.
- steveklabnik 10y ago"Why is this posted here" is not really constructive criticism, because again, this post isn't written for a broader audience, it just happened to be posted here. Every single project blog isn't going to re-iterate every single detail just in case it takes off with a broader audience. I do agree that that post is pretty great; I loved the series. But it's trying to accomplish something different than this post is.
- Manishearth 10y agoWhat are you criticizing here? You're ultimately criticizing the HN community for upvoting a topic you're not interested in, which IMO is absurd, you're telling people what to be interested in. Either that, or you're criticizing the blog post author for not covering all audiences, which is also absur, folks are allowed to target audiences. This isn't really constructive. Like Steve said, this post wasn't written for a general audience. A Rustacean will read that post and will be very happy to know that they can do certain things using pure Rust libraries. That was the audience of the post, the post makes total sense in that context, and has inherent value in that context. It got shared more widely, and HN seems to like it, which means that possibly folks who weren't the original intended audience are reading it, which is okay too, just that they may not find it that interesting.
- pjmlp 10y agoFor example, I do care, even if I don't use Rust professionally, because in the future those native libraries that I actually use in Java and .NET, might eventually be rewritten in Rust, thus making our clients enjoy a more safer stack.