News for hackers. Stuff that matters.
Re:A Sad Day for Rust by C14L on Friday January 17, 2020 @01:49PM (#22077796)
Or fork the code. That's the great thing about FOSS.
Re:A Sad Day for Rust by sendilkumarn on Friday January 17, 2020 @02:53PM (#22078489)
This could have solved a lot of problems...
Re:A Sad Day for Rust by mratsim on Friday January 17, 2020 @07:05PM (#22081065)
and introduce new flamewars about "Not-Invented-Here", why don't you contribute to a common codebase, ffmpeg vs libav/avconv debacle.
Re:A Sad Day for Rust by pgeorgi on Saturday January 18, 2020 @02:49AM (#22083051)
ffmpeg / libav had lots of bad blood long before the fork, which might have been the real driver for making it a "debacle".

GitHub in particular has a "fork" button to make it super-easy. So fork, do your edits. If you want, make a pull request with the original project. If they take it, great: the fork can cease to exist.

If they don't want to merge it don't take it personally but go your own merry ways. And this is what didn't happen with actix.

Re:A Sad Day for Rust by anon463637 on Saturday January 18, 2020 @02:43AM (#22083028)
Forking if it's mature and featured enough to justify it, but it maybe too unsafe broken to invest in rewriting large swaths of code. That's the perpetual trade-off of engineering decisions; whether to build, fork or buy.