<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">I'm also largely ok with it, provided we do what we can to keep external crate use to a minimum. I don't know what Rust is doing to avoid their own version of NPM's "ldap moment" (or ansi-color or whatever that bit us directly) but I'd rather not find out first-hand.<div><br></div><div>Unfortunately while I have had interest in learning more with Rust but haven't been able to actually make the time to do it. I suppose this would finally give me more incentive. :)</div><div><br></div><div>I know "should we replace all of the 'C'?" wasn't really Bill's original question but I do think that we're more likely to find folks<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"> that can</span><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"> </span><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">(or more quickly learn) to</span> write correct and safe Rust than C in the long run. </div><div><br></div><div>Jason<br><div>
<meta charset="UTF-8"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div><br>-- <br>Jason Boyer<br>Senior System Administrator<br>Equinox Open Library Initiative<br>JBoyer@equinoxOLI.org<br>+1 (877) Open-ILS (673-6457)<br>https://equinoxOLI.org/</div></div></div></div>
</div>
<div><br><blockquote type="cite"><div>On May 31, 2023, at 9:53 AM, Jason Stephenson via Evergreen-dev <evergreen-dev@list.evergreen-ils.org> wrote:</div><br class="Apple-interchange-newline"><div><div>Bill,<br><br>I am OK with adopting Rust as a supported language. I might even be in favor of replacing all of our C code with Rust eventually.<br><br>I have not done anything with Rust so far. I have been meaning to try it out.<br><br>Cheers,<br>Jason Stephenson<br>_______________________________________________<br>Evergreen-dev mailing list<br>Evergreen-dev@list.evergreen-ils.org<br>http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev<br></div></div></blockquote></div><br></div></body></html>