3 ms·
From the title, my guess was this was going to be an interesting case of someone publicly admitting a mistake, in some lesson we could all learn from. Instead,
by neilv 3y ago
From the title, my guess was this was going to be an interesting case of someone publicly admitting a mistake, in some lesson we could all learn from.
Instead, the title functions as a clickbaity hook, to promote the fork that the author is ostensibly apologizing for making.
(I don't know whether the fork is good, bad, or neither. Just, probably I should've guessed what the most likely meaning of the title would be.)
- lovasoa 3y agoHey, I'm the author of the post. I did not post it to hacker news, but to the r/rust subreddit, where I think people had more context, and more reasons to be interested in it. Someone else posted the link to hacker news. The title (which I indeed wanted to be a good catch phrase) was not meant to be an apology. English is not my mother tongue, so I may be misguided, but I meant "sorry" as "I am sorry about the state of affairs", not literally "I apologize to you, the sqlx library".
- aukaost 3y agoMaybe "I'm sorry I had to fork you" would've been more in line with what you meant to say?
- orbz 3y agoAdding a ‘but’ in there is often times used to negate everything before the but, like “I’m sorry but I had to fork you” would imply you’re not sorry, you had to do this.
- neilv 3y agoThank you, I understand.
- rowyourboat 3y agoI don't think the fact that it's sqlx or rust is really relevant. What you're describing is a problem and conflict of interest that's pervasive on open source, and that's what I thought worthy of discussing on hn. I'm sorry that people seem to focus on your use of the word sorry, I read it to mean in the sense of "it's a shame that the world is how it is".
- lovasoa 3y agoYes that's what I meant.