diff options
Diffstat (limited to '_posts')
| -rw-r--r-- | _posts/2020-08-10-guix-inside-sourcehut-builds-sr-ht-ci.md | 2 | ||||
| -rw-r--r-- | _posts/2020-08-31-the-database-i-wish-i-had.md | 12 |
2 files changed, 7 insertions, 7 deletions
diff --git a/_posts/2020-08-10-guix-inside-sourcehut-builds-sr-ht-ci.md b/_posts/2020-08-10-guix-inside-sourcehut-builds-sr-ht-ci.md index dcda7f4..3ce2acf 100644 --- a/_posts/2020-08-10-guix-inside-sourcehut-builds-sr-ht-ci.md +++ b/_posts/2020-08-10-guix-inside-sourcehut-builds-sr-ht-ci.md @@ -117,7 +117,7 @@ or run any `guix environment --ad-hoc my-package -- my script` :) When I originally created this code I had a reason why to have both a `sudo` call for `sudo ./scripts/install-guix.sh` and `sudo` usages inside `install-guix.sh` itself. I couldn't figure out why (it feels like my past self -was a bit smarter xD), but it feels ugly now. If it is truly required I could +was a bit smarter 😬), but it feels ugly now. If it is truly required I could add an explanation for it, or remove this entirely in favor of a more elegant solution. I could also contribute the Guix image upstream to builds.sr.ht, but there diff --git a/_posts/2020-08-31-the-database-i-wish-i-had.md b/_posts/2020-08-31-the-database-i-wish-i-had.md index 8065696..7bb0036 100644 --- a/_posts/2020-08-31-the-database-i-wish-i-had.md +++ b/_posts/2020-08-31-the-database-i-wish-i-had.md @@ -78,7 +78,7 @@ makes it inherit most of the downsides (and benefits too) of SQLite itself. [mentat]: https://github.com/mozilla/mentat Having such a requirement imposes a different approach to storage: we have to -decouple the knowledge about the intricansies of storage from the usage of +decouple the knowledge about the intricacies of storage from the usage of storage itself, so that a module (say query processing) can access storage through an API without needing to know about it's implementation. This allows the database to target a POSIX filesystems storage API and an IndexedDB storage @@ -89,10 +89,10 @@ mechanism (called [adapters][pouchdb-adapters]) and Datomic has them too (called [pouchdb-adapters]: https://pouchdb.com/adapters.html [datomic-storage-services]: https://docs.datomic.com/on-prem/storage.html -This would allow the database to adapt to where it is embedded: when targetting +This would allow the database to adapt to where it is embedded: when targeting the browser the IndexedDB storage API would provide the persistence layer that the database requires, and similarly the POSIX filesystem storage API would -provide the persistence layer when targetting POSIX systems (like desktops, +provide the persistence layer when targeting POSIX systems (like desktops, mobile, etc.). But there's also an extra restriction that comes from by being embedded: it @@ -119,11 +119,11 @@ information (datoms) and allows you to query them in a multitude of ways. Stuart Halloway calls it "accumulate-only" over "append-only"[^accumulate-only]: > It's accumulate-only, it is not append-only. So append-only, most people when -> they say that they're impliying something physical about what happens. +> they say that they're implying something physical about what happens. [datomic]: https://www.datomic.com/ [^accumulate-only]: Video "[Day of Datomic Part 2](https://vimeo.com/116315075)" - on Datomic's infomation model, at time 12:28. + on Datomic's information model, at time 12:28. Also a database can be append-only and overwrite existing information with new information, by doing clean-ups of "stale" data. I prefer to adopt the @@ -220,7 +220,7 @@ Cantrill. ### Portability -Being able to target so many differente platforms is a bold goal, and the +Being able to target so many different platforms is a bold goal, and the embedded nature of the database demands portability to be a core value. ### Integrity |