it can go both way!

Posted Nov 22, 2024 20:51 UTC (Fri) by ballombe (subscriber, #9523)
Parent article: NonStop discussion around adding Rust to Git

If one allows developers to replace some C code to rust, as a matter of fairness one should allow developers to port some rust code back to C!

it can go both way!

Posted Nov 23, 2024 1:51 UTC (Sat) by dvdeug (guest, #10998) [Link] (4 responses)

Why? The point of replacing C with Rust is that it's more reliable and easier to maintain, while being reasonably as fast. There's no fairness involved; changes between languages should be for rational reasons, not territorial ones.

it can go both way!

Posted Nov 23, 2024 8:52 UTC (Sat) by Wol (subscriber, #4433) [Link] (3 responses)

I think you're missing the tongue-in-cheek.

There are probably a lot more developers (famliar with Rust) who would like to contribute but are crap at C, than there are good C developers who would like to port from Rust to C.

Cheers,
Wol

it can go both way!

Posted Nov 23, 2024 20:27 UTC (Sat) by jhoblitt (subscriber, #77733) [Link] (2 responses)

In that vein...

The size of one of those groups is zero because there aren't any devs that aren't crap at C. There are, at best, devs who don't understand that they are crap at C.

it can go both way!

Posted Nov 23, 2024 21:51 UTC (Sat) by pizza (subscriber, #46) [Link] (1 responses)

> The size of one of those groups is zero because there aren't any devs that aren't crap at C. There are, at best, devs who don't understand that they are crap at C.

The same can be said about *any* human endeavor.

...Meanwhile, continue to crap all over those who write the code you depend on. I'm sure that will convince them of your non-crappiness.

it can go both way!

Posted Nov 23, 2024 23:10 UTC (Sat) by jhoblitt (subscriber, #77733) [Link]

I think you're missing the tongue-in-cheek.