prepor

https://github.com/electric-sql/electric/blob/main/clients/t...

  // Once we have electric, we then establish the data change
  // notification subscription, comparing the tablenames used by the
  // query with the changed tablenames in the data change notification
  // to determine whether to re-query or not.
  //
  // If we do need to re-query, then we use the saved function to reuse the query

Writes automatically cause any relevant live queries to update.

How do you decide what queries are relevant?

If anyone has success integrating Prolog in modern software please share, I'm really curious.

https://terminusdb.com/ is almost entirely written in prolog. + a little bit of Rust and JS.

Check data sheets for any 3d printing filament, Young’s modulus is the main characteristic in them and that's how you can reason about filament abilities.

For example, https://cdn.shopifycdn.net/s/files/1/0584/7236/6216/files/Ba...

Based on what I read it's very similar to Kafka Streams + batteries ([semi]automatic workload orchestration, reactive queries, higher-level/slicker/"smarter" API (?))

Could you please compare Rama with Kafka Streams, especially from the point of view, if I would try to reimplement Rama API on top of Kafka Streams? What fundamental difficulties I'd face?

Electric could be an ideal companion to these reactive Queries & Depots to build actual UI, btw

Why don't we just use Reactjs?

"Dealing with immutable data in JavaScript is more difficult than in languages designed for it, like Clojure. "

From React's docs.

It's not here yet, but we are planning to add it soon

You can do everything that you can with typeclasses without them. In fact GHC compiles Haskell into GHC core, where are no typeclasses.

See http://okmij.org/ftp/Computation/typeclass.html