fix: minor typos

This commit is contained in:
Timothy DeHerrera
2025-05-18 23:14:37 -06:00
parent 53de196884
commit ba0daf07c1
2 changed files with 2 additions and 2 deletions

View File

@@ -207,7 +207,7 @@ Now, lets dive into the Atom Nix language API and explore how it harnesses th
## Atomic Nix
With the atom URI paving the way for user-friendly access, were ready to explore the high-level Atom Nix language frontend. As Ive said, atom is fundamentally a packaging API. Weve dissected the Ekala Git store as a storage backend; now its time to unpack what a language frontend needs to mesh with the atom protocol. This depends heavily on the languages built-in facilities—or lack thereof. Take Rust: integrating Cargo crates with atom would be a breeze, since Cargo already provides a slick, consistent frontend. Itd likely just need atom as a dependency in the `cargo` binary and some glue code to tie it together.
With the atom URI paving the way for user-friendly access, were ready to explore the high-level Atom Nix language frontend. As Ive said, Atom is fundamentally a packaging API. Weve dissected the Ekala Git store as a storage backend; now its time to unpack what a language frontend needs to mesh with the atom protocol. This depends heavily on the languages built-in facilities—or lack thereof. Take Rust: integrating Cargo crates with atom would be a breeze, since Cargo already provides a slick, consistent frontend. Itd likely just need atom as a dependency in the `cargo` binary and some glue code to tie it together.
Were not rushing to support existing formats like Cargo while atoms still young, but I bring it up to contrast with Nix. Unlike Rust, Nix has almost no native tools for neatly packaging or isolating its code. Building an atom frontend for Nix means crafting core pieces from scratch to make it work.