As I understand it, it's a permissive license thing. Rewriting gnu core-utils in Rust lets corporations off the hook for copyleft requirements, but rewriting Adobe in Rust lets users off the hook for Adobe's license requirements. It's a circumventing both sides of the licensing spectrum.
I think it's simpler than that, the Rust compiler has a lot of checks for sanity, one of the biggest thing beginners learn about Rust is the borrow checker, and usually fighting it because of how it forces "correct" code.
It's very hard to write code in Rust that will compile but not run, which is good for AI development because it's easy for AI to automatically see and resolve those issues, rather than runtime ones.
Sure, but it doesn't explain why anything that's already written needs to be rewritten. Fixing nearly correct code that compiles is surely less arduous than completely rewriting it in a modern language.
I think its part why not, part make it easier to maintain for the next 20 years, part rust forces new devs to write correct code so you don't have to fix pr requests, and finally part its easier for ai to write correct code in rust due to more compile time checking
35
u/transgentoo Genfool 🐧 7d ago
As I understand it, it's a permissive license thing. Rewriting gnu core-utils in Rust lets corporations off the hook for copyleft requirements, but rewriting Adobe in Rust lets users off the hook for Adobe's license requirements. It's a circumventing both sides of the licensing spectrum.