34
Is there an easier way forward for rust in linux?
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 Feb 2025
34 points (87.0% liked)
Linux
6466 readers
604 users here now
A community for everything relating to the GNU/Linux operating system
Also check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
Perhaps the problem is you wanting developers to work on something they don't want to work on.
The problem is wanting to shoehorn a new language into an existing, long-standing large-codebase project.
Forking is the obvious solution but rustaceans know that's a pretty daunting task...
The next best thing is to develop in parallel, refactoring parts (usually drivers) without interfering with the existing codebase.
Forking does not solve the problem, it only escapes it. Its waste of time and effort in this case. The solution is that the devs work together. Otherwise it makes no sense to have Rust if no one works together. Discussion is the best way to handle this and to come to a solution. Its such an important topic that you have to discuss it, this is healthy, this is how it should be done. This is how its done.
If people can't work together, forking usually "solves" the problem.
Let's see if they end up working together.
Forking does not solve the problem, it escapes it. The problem in the main Rust Kernel will stay, not working together, arguing, while the fork might work for those who work on the fork. This is not a driver or feature where they can fork, work on it separately. It completely misses the point.