From 89eb93a932c9e2e68b1b0c5827e6be7ee390ed38 Mon Sep 17 00:00:00 2001 From: Timothy DeHerrera Date: Sat, 7 Dec 2024 18:45:09 -0700 Subject: [PATCH] fix: grammar correction --- src/content/blog/nix-to-eos.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/blog/nix-to-eos.md b/src/content/blog/nix-to-eos.md index 8e388a7..c22c252 100644 --- a/src/content/blog/nix-to-eos.md +++ b/src/content/blog/nix-to-eos.md @@ -117,7 +117,7 @@ At its core, `eka` serves as an atomic frontend to a backend service that handle 3. Improved addressing: While flakes introduced useful URI shorthand, we've expanded this concept with Atom URIs. Unlike flakes' hard-coded shortcuts, Atom URIs are configurable, allowing patterns like `work:repo::my-atom@^1`. Crucially, these always expand to full URLs in the final output, ensuring universal understanding while maintaining convenience. -To support this ambitious scope, we plan to implement a language-agnostic plugin system for `eka`. While the core remains focused on efficient atomic operations and basic backend communication, plugins will extend functionality through a well-defined API surface. This extensibility will become increasingly important as `eka` evolves, and to help avoid bloat and complexity in the core codebase. +To support this ambitious scope, we plan to implement a language-agnostic plugin system for `eka`. While the core remains focused on efficient atomic operations and basic backend communication, plugins will extend functionality through a well-defined API surface. This extensibility will become increasingly important as `eka` evolves to help avoid bloat and complexity in the core codebase. The ultimate vision for `eka` users is efficient querying of packages, deployment manifests, and configurations across their organization and the open-source landscape—all without upfront Nix evaluation. It should optimize away unnecessary evaluations and builds when artifacts exist in cache, in concert with the backend, proceeding directly to fetching. If `eka` ever needs to perform evaluation for value generation, we've strayed from our design goals.