News for hackers. Stuff that matters.
Re:A Sad Day for Rust by streb-lo on Friday January 17, 2020 @10:33AM (#22075445)
Exactly this.

If it doesn't meet your standards, don't use it.

Alternatively, go fork yourself.

Re:A Sad Day for Rust by silon42 on Friday January 17, 2020 @10:36AM (#22075487)
Personally I plan to vendor all dependencies.

It would be nice to have cargo/rustc support 'allow_unsafe' per module and also for dependencies, so you know you have to review a dependency really well.

Re:A Sad Day for Rust by ksec on Friday January 17, 2020 @10:43AM (#22075562)
>If it doesn't meet your standards, don't use it.

>Alternatively, go fork yourself.

I think this could be the new template for Open Source Author to include in their OS work description should they choose to.

Re:A Sad Day for Rust by guscost on Friday January 17, 2020 @10:53AM (#22075685)
This is my new CONTRIBUTING.md file for personal projects. Thanks!
Re:A Sad Day for Rust by mratsim on Friday January 17, 2020 @01:13PM (#22077407)
But then you get drama about Not-Invented-Here, why are you creating yet-another-X-framework instead of improving the existing ones.

Or you get drama like ffmpeg vs libav/avconv.

Re:A Sad Day for Rust by bloodorange on Friday January 17, 2020 @03:19PM (#22078772)
Indeed. Many times, making a real effort and doing something has a real cost and risk associated with it. This is unlike demanding that someone else offer services which solve one's problem(s) while not offering any payment for it. The latter approach has minimal cost: it only harms one's dignity.
Re:A Sad Day for Rust by rusttoxic on Friday January 17, 2020 @10:35AM (#22075483)
The only time ever on earth where a homophone actually has been done well. Thank you.