Skip to content

Commit 68b1f1d

Browse files
authored
Update README.md
1 parent e8b8775 commit 68b1f1d

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

README.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,7 @@
3535
- [Store Values in Custom UserDefaults](#store-values-in-custom-userdefaults)
3636
- [Store Values Under Custom Key](#store-values-under-custom-key)
3737
- [Using with @AppStorage](#using-with-appstorage)
38+
- [🤔 Why "Spices"?](#-why-spices)
3839

3940
## 👋 Introduction
4041

@@ -478,3 +479,11 @@ struct ExampleView: View {
478479
}
479480
}
480481
```
482+
483+
## 🤔 Why "Spices"?
484+
485+
The name "Spices" evolved from our original repository, "ConfigVars", which we used internally at [Shape](https://shape.dk) (becoming [Framna](https://framna.com)) for several years. That early version didn’t use reflection, but when we experimented with a new implementation that did, we jokingly called it "spicing it up." The idea stuck, and we realized developers could also use the package to "spice up" their own projects, adding extra debugging "spices" as needed.
486+
487+
For the first few years, the project was called "Config Vars", but we never really loved that name. It felt too generic. When we decided to open-source the package, we considered reverting to the original name or using other generic alternatives like "configs," "variables," "tweaks," or "configuration variables."
488+
489+
However, these terms are so widely used and have so many different meanings that we worried about causing naming conflicts in developers' codebases. Ultimately, we stuck with "Spices" because it’s unique, memorable, and less likely to clash with existing concepts.

0 commit comments

Comments
 (0)