News for hackers. Stuff that matters.
Re:Async Rust is not safe with io_uring by airstrike on Wednesday October 30, 2024 @10:55AM (#41995640)
I look forward to your blog post running the code provided by the article and rebutting it

And I mean that honestly, no sarcasm at all!

Re:Async Rust is not safe with io_uring by infamouscow on Wednesday October 30, 2024 @11:44AM (#41996408)
You're replying to the author of ringbahn, whom also happens writes some of the best technical blog posts ever to grace this website on these topics.

It is very difficult not to conclude you're either very ignorant, or trolling.

Re:Async Rust is not safe with io_uring by airstrike on Wednesday October 30, 2024 @11:52AM (#41996498)
What makes you think I don't know who I'm talking to? All I was trying to do was encourage another blog post. I literally went out of my way to try to sound nice and preemptively dismiss the chance that I was interpreted sarcastically.

https://news.ycombinator.com/newsguidelines.html

> Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith.

Re:Async Rust is not safe with io_uring by infamouscow on Wednesday October 30, 2024 @08:48PM (#42002286)
You didn't actually ask or open a dialogue; you made a prescriptive statement with a built-in expectation. When you say, "I look forward to your blog post" you're essentially assigning them work based on your own interpretation of their interests.

It’s not really about whether you sound nice or if sarcasm is preemptively dismissed. The problem is that there's no actual invitation or question and it comes across as presumptive and entitled.

What makes it even harder to take seriously is the follow-up: "[a]nd I mean that honestly, no sarcasm at all!" That line doesn't sit well, because it suggests you knew how it might come across but chose to push it anyway. A bit more curiosity or an open-ended question could have made all the difference here.

Re:Async Rust is not safe with io_uring by itishappy on Wednesday October 30, 2024 @11:48AM (#41996442)
Alternative explanation: They're a fan!
[dead]
Re:Async Rust is not safe with io_uring by airstrike on Wednesday October 30, 2024 @11:41AM (#41996341)
I truly must be for ever wanting to read a post by someone who talks to their readers like this. I even went out of my way to say I wasn't being sarcastic.

Let us part ways, then, and in the meantime I encourage you to find the light you must be missing in your life.

Re:Async Rust is not safe with io_uring by withoutboats3 on Wednesday October 30, 2024 @11:53AM (#41996506)
My sincere apologies if I read this uncharitably, I interpreted your comment about sarcasm to itself be sarcastic. I will not be publishing any such post.

To clarify what you seem not to understand: the code in the blog post depends on a library called monoio, and based on the post's description of the behavior of that code (I haven't actually read the source for monoio), monoio contains a bug. I don't dispute that this code behaves incorrectly, just that it has anything to do with Rust's facility for async IO rather than with the specific IO library employed in the post.

Re:Async Rust is not safe with io_uring by throw-away_42 on Wednesday October 30, 2024 @12:10PM (#41996772)
Master of being condescending, too.
Re:Async Rust is not safe with io_uring by dang on Thursday October 31, 2024 @03:02PM (#42010262)
I know the GP comment was provocative, but please don't respond to a bad comment by breaking the site guidelines yourself. That only makes things worse.

https://news.ycombinator.com/newsguidelines.html

Edit: this has been a problem in other places too:

https://news.ycombinator.com/item?id=41657430

https://news.ycombinator.com/item?id=41034778

Could you please not post like this to Hacker News? It's not what this site is for, and destroys what it is for. (https://news.ycombinator.com/item?id=41996506 was much better, of course.)

If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.

Re:Async Rust is not safe with io_uring by ryansouza on Wednesday October 30, 2024 @01:44PM (#41998086)
Even without sarcasm the wording here reads as a presumption that this person will do work (blog post) for your benefit. Their post not indicating any plans to do that is why it reads so sarcastically, a sort of “pull requests welcome” reply in a more rude way.
Re:Async Rust is not safe with io_uring by dang on Thursday October 31, 2024 @02:55PM (#42010194)
I believe that you didn't intend to, but you started a flamewar with this comment. Others responded poorly, but the provocation started here.

One thing that might be helpful to know is that you saying you intend your comment a certain way isn't sufficient to remove the provocation from it. You have to show, not just tell, your intent.

In this case the first sentence was too confrontational for the second sentence to overcome the impression you were giving; as a result, people actually interpreted it as extra sarcastic.

Some past explanations that may (or not) be helpful: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

(We detached this subthread from https://news.ycombinator.com/item?id=41994146.)

Re:Async Rust is not safe with io_uring by airstrike on Thursday October 31, 2024 @04:34PM (#42011225)
FWIW I most definitely did not intend it! I meant in good faith to say I was a fan of their blog. Oh well. Lesson learned and I'll be more careful with my word choices and spend a little longer re-reading before hitting "submit"