A Sad Day for Rust

Re:A Sad Day for Rust by jessaustin on Friday January 17, 2020 @10:35AM (#22075473)

In that case, you clone and fork. If you're just trying to get your stuff working, your fork is private. If instead you're trying to enjoy publicity, you publicize your fork. In neither case is it necessary to annoy someone who has already done a lot of free work for you.

[ Parent | on HN ]

Re:A Sad Day for Rust by jimbokun on Friday January 17, 2020 @10:43AM (#22075570)

Reporting bugs is annoying?

I want people to point out bugs in my code, so both my code and me as a developer can improve.

[ Parent | on HN ]

Re:A Sad Day for Rust by jessaustin on Friday January 17, 2020 @10:54AM (#22075696)

This isn't a serious response. As amply demonstrated in TFA and elsewhere, the harassment was far more than "reporting bugs".

And, anyway, yes, reporting bugs can be extremely annoying. Different devs respond to this annoyance differently. npm devs, for example, have decided not to pay too much attention to bugs reported by the public. [0]

[0] https://npm.community/c/bugs

[ Parent | on HN ]

Re:A Sad Day for Rust by Razengan on Friday January 17, 2020 @02:14PM (#22078067)

> And, anyway, yes, reporting bugs can be extremely annoying.

I would never touch the product of someone who found bug reports annoying.

[ Parent | on HN ]

Re:A Sad Day for Rust by lenkite on Friday January 17, 2020 @04:12PM (#22079399)

Strangely, I would rather deal with developers who find bug reports annoying than folks who simply ignore them. The former have a touch of pride and you have a chance to get them to see your point of view. Better that than speaking to a black-hole.

[ Parent | on HN ]

Re:A Sad Day for Rust by jessaustin on Saturday January 18, 2020 @03:15PM (#22086837)

That's a good policy, both for you and for them.

[ Parent | on HN ]