https://robertcarson.org/tags/crystallography/Recent content in Crystallography on Robert CarsonHugo -- gohugo.ioen© 2026 Robert CarsonTue, 15 Apr 2025 00:00:00 +0000https://robertcarson.org/projects/rust_projects/Tue, 15 Apr 2025 00:00:00 +0000https://robertcarson.org/projects/rust_projects/<h2 class="relative group">Why Rust <div id="why-rust" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-rust" aria-label="Anchor">#</a> </span> </h2> <p>Before any specific library, some context on the language. The motivation was not ideological. It was practical and rooted in a specific kind of pain: Fortran code that compiles and runs without complaint, but quietly passes array shapes that do not match what the calling code believes they are. No runtime check, no compiler error, just wrong numbers. That class of silent bug had bitten me enough times that when a new language showed up that made memory safety a first-class guarantee enforced at compile time, it was worth learning seriously. Rust became the language I reached for when exploring new ideas or building tools where correctness under the surface mattered as much as correctness of output. Over time it also became a practical choice for building fast Python libraries through PyO3 bindings, since you get native execution speed with an interface that scientific users can drive from notebooks and scripts without knowing anything about Rust.</p>