Can anyone explain why do we need this rewrite? What I’m hearing is just that the language is memory safe and, honestly, it sounds like a weak argument. Unless the program is actively evolving or requires regular updates and it can be seen that a rewrite could genuinely improve things…
All I’ve seen in these media posts were just vague “what if” arguments. If that’s it, a rewrite seems pretty dumb.
Image working in an old building, there is no coffee machine, there is no warm water and if you want to do something new, chances of you getting in trouble because you forgot to mess with CMake or free memory, are high.
But the building works since it has been tested for 30 years.
Rust is a new building that you can move over to, there is a coffee machine that is a bit complicated at first but once you understand it it is that bad, there is warm water and you don’t have to mess with CMake or allocate/free memory for everything.
But the building is new, there will be issues here and there and sometimes the promised warm water wont work since someone fucked it up, but in general it is just sooooo much more comfy to work in.
Rust is not about making Programming languages fast or memory safe. If you truly want to do that, I recommend doing crack and writing in assembly.
It is about making programming easier without sacrificing speed.
OK, imagine youre in a new car and youre like hmm donuts are good. But you know that when flight was first discovered it was scary, then after all that scares you knew it was worth while running the distance. Sometimes you gotta know when to fold em.
Sudo is being actively developed and has several fairly recent CVEs, some of which are memory issues (at least recent compared to how old sudo is). Apart from being memory safe rust is also better at error handling than C.
IMO best would be to reduce attack surface by using a memory safe language and also reducing complex features like OpenBSD’s doas does.
That’s honestly more of a problem than a feature at this point. The GPL at least protects open source projects as a “public good” and forces corporate users to contribute their changes back to the public (in some manner). All permissive licenses do is let corporations leech off the community without a requirement to give back.
Can anyone explain why do we need this rewrite? What I’m hearing is just that the language is memory safe and, honestly, it sounds like a weak argument. Unless the program is actively evolving or requires regular updates and it can be seen that a rewrite could genuinely improve things…
All I’ve seen in these media posts were just vague “what if” arguments. If that’s it, a rewrite seems pretty dumb.
Image working in an old building, there is no coffee machine, there is no warm water and if you want to do something new, chances of you getting in trouble because you forgot to mess with CMake or free memory, are high. But the building works since it has been tested for 30 years.
Rust is a new building that you can move over to, there is a coffee machine that is a bit complicated at first but once you understand it it is that bad, there is warm water and you don’t have to mess with CMake or allocate/free memory for everything. But the building is new, there will be issues here and there and sometimes the promised warm water wont work since someone fucked it up, but in general it is just sooooo much more comfy to work in.
Rust is not about making Programming languages fast or memory safe. If you truly want to do that, I recommend doing crack and writing in assembly. It is about making programming easier without sacrificing speed.
I agree with you completely, but good god man, if you’re going to use a metaphor stick with it.
OK, imagine youre in a new car and youre like hmm donuts are good. But you know that when flight was first discovered it was scary, then after all that scares you knew it was worth while running the distance. Sometimes you gotta know when to fold em.
Sudo is being actively developed and has several fairly recent CVEs, some of which are memory issues (at least recent compared to how old sudo is). Apart from being memory safe rust is also better at error handling than C.
IMO best would be to reduce attack surface by using a memory safe language and also reducing complex features like OpenBSD’s doas does.
https://www.cvedetails.com/vulnerability-list/vendor_id-15714/Sudo-Project.html?page=1&order=3
Well, if they make it good, it has a permissive license and future updates and forks can take it private.
That’s honestly more of a problem than a feature at this point. The GPL at least protects open source projects as a “public good” and forces corporate users to contribute their changes back to the public (in some manner). All permissive licenses do is let corporations leech off the community without a requirement to give back.