4 ms·
> Best Current Practises > 1. Authors MUST NOT implement bugs. This, of course, is achieved by writing the software in Rust. Writing software in Rust avoids,
by codetrotter 5y ago
> Best Current Practises
> 1. Authors MUST NOT implement bugs.
This, of course, is achieved by writing the software in Rust.
Writing software in Rust avoids, not only memory corruption type bugs, but indeed it is impossible to implement any sort of defect, as long as you write your software in Rust.
/ducks
- vlowther 5y agoInstructions unclear, now suffering from waterfowl infestation. I think some of them are geese.
- rurban 5y agoThis of course is achieved by writing software in a safe language. would be nice if Rust someday would join this group. their bug tracker speaks otherwise, and their docs and specs ditto.
- gnufx 5y agoOK, hands up all those who were about to post something similar.
- wongarsu 5y agoAlternatively write your software in Go. Go is not only memory safe, it's also easy. So easy that it's basically impossible to write bugs in any Go program.
- jart 5y agoAlternatively write your software in Java. Java is not only memory safe, it's also approved by your corporate overlords. So authorized that it's basically impossible to write bugs in any Java program, except for ones like Mad Gadget vulnerability and Log4j.
- 8n4vidtmkvmk 5y agolog4j was a feature, not a bug.
- jart 5y agoHow rude! [RFC9225 §4.4]
- js8 5y agoWrite it in Haskell, if it compiles, it will be correct. Or "write it" in Java, there already is a framework to solve your very problem, all you need to do is to configure it in X.. ehm, YAML. Or just do it all in the frontend, if there is a bug, worst case, user can always reload the page and start over. Also, never write any specification or documentation. That way, the program is guaranteed to do exactly what it does.
- nightfly 5y ago> Or "write it" in Java, there already is a framework to solve your very problem, all you need to do is to configure it in X.. ehm, YAML. Nah, modern java needs still needs configuration in XML, YAML, _and_ environment variables set in shell scripts somewhere. And maybe stored in your LDAP server too ;)
- dottedmag 5y agoI have worked for a company with a coding standard that included the following sentence: (quoting) "Do not write bugs in the code". The temptation to use commit message "fixing coding standard violation" for bugfixes was palpable.