diff options
| -rw-r--r-- | IDEAS.org | 6 | ||||
| -rw-r--r-- | blog/content/notes/tech/motivating-example-for-logical-replication-for-dynamic-ui.gmi | 2 |
2 files changed, 7 insertions, 1 deletions
@@ -141,6 +141,12 @@ The mirror requests /foo to httpd, which returns the gemtext. - Provides a UI to approve individual commits - For validated *and* approved commits, it implements a merge queue that works on a per-commit basis. +* Jerarco + +- Classifies items of a certain kind (e.g. links to projects) +- Each item can have multiple hierarchical tags (e.g. software/for/end-users, software/implemented-in/python, maths/graph-theory, etc.) +- Jerarco builds a "flat" categorization by taking the leaf tag with most items and printing all elements in that leaf tag, then removing the items from the list, and iterating until there are no more items. + * Complexity explorer (Acomplejator) - Qualifies a set of files (by programming language, type of asset [lock file, documentation, etc.], etc.) diff --git a/blog/content/notes/tech/motivating-example-for-logical-replication-for-dynamic-ui.gmi b/blog/content/notes/tech/motivating-example-for-logical-replication-for-dynamic-ui.gmi index daf5329e..01fc5fae 100644 --- a/blog/content/notes/tech/motivating-example-for-logical-replication-for-dynamic-ui.gmi +++ b/blog/content/notes/tech/motivating-example-for-logical-replication-for-dynamic-ui.gmi @@ -20,7 +20,7 @@ Imagine you could write an UI element that subscribed to the following publicati create publication foo for table chat_messages where (channel in :list_of_channels_user_is_in and posted > :some_time_ago); ``` -Without writing any additional code, the UI element would get instantly notified not only of all new messages, but also of editions, deletions, or messages moved in or out of the subscribed channels. I believe you could write a real-time UI element with much shorter and safer code than any alternative I can think of that only uses OSS code. (As far as I know, [ksqlDB](https://github.com/confluentinc/ksql) does a similar thing, but has non-OSS bits and seems much harder to deploy than PostgreSQL, besides you would also need to deploy PostgreSQL.) +Without writing any additional code, the UI element would get instantly notified not only of all new messages, but also of editions, deletions, or messages moved in or out of the subscribed channels. I believe you could write a real-time UI element with much shorter and safer code than any alternative I can think of that only uses OSS code. (As far as I know, ksqlDB does a similar thing, but has non-OSS bits and seems much harder to deploy than PostgreSQL, besides you would also need to deploy PostgreSQL.) This has some caveats: |