top | item 19224566

Datomic, Datalog, GraphQL, APIs, etc.

177 points| tosh | 7 years ago |tank.hyperfiddle.com | reply

11 comments

order
[+] rmbryan|7 years ago|reply
If "Hyperfiddle is after more of a vision where like, what would it take for my mom or my future kids to be programmers and yet not be professional software engineers." then I suggest you focus on drastically simplifying the vocabulary you use to explain what Hyperfiddle is.

For example: "This is a pastebin like environment for learning Hyperfiddle. Please namespace :idents with your username Schema changes are allowed To make a fiddle interactive, change tank.hyperfiddle.net to demo.hyperfiddle.net"

My mom no grok: pastebin, :idents, namespace as a verb, schema, "change" without a where to change.

Granted, this is a conversation between to engineers, so there's lexicon, but even listening, I get the sense that words get used without definition, or at least without a definition that speaker and listener share.

[+] dustingetz|7 years ago|reply
For those out of the loop - At Hyperfiddle we are building a tool for Clojure/Datomic programmers to make back of house dashboards easily. http://www.hyperfiddle.net/ Because Hyperfiddle/Datomic has such a simple information model, we see a path to eventually making this easy enough for code-savvy amateurs. But today you need to know Clojure.
[+] frankmcsherry|7 years ago|reply
For some context on "what Niko presented at the Conj",

    https://2018.clojure-conj.org/nikolas-gobel/
which is a reactive Datalog implementation built over differential dataflow. The .. um reported anxiety that to add new queries requires a recompile loop, replaying all of history, etc, suggests maybe they aren't entirely on top of how the system works.

Edit: and again tomorrow at clojureD:

    https://clojured.de/schedule/#nikolasGoebel
[+] dustingetz|7 years ago|reply
hi Frank, we are definitely not entirely on top of this stuff, but it is very awesome and we will get there eventually :)

Can you help me understand where we went awry here:

"Now of course the problem there with a rules engine... I have to look at the incremental dataflow, but I imagine it's kind of the same sort of approach. The problem with that is that if you want to sort by a new thing or you have a new piece of information, you have to change the network and backflow any... [You have to know compile time...] Yeah. Yeah. Exactly. And there are systems where you can add a new rule at runtime, but a lot of those also involve then re-ingesting history into the network to repopulate anything they... 'Cause a lot of these systems to save memory, will just throw away any information you're not interested in, from compiled query."

If we are close can you tighten up the language and if we are far where did we go wrong? (In the context of differential dataflow, not rules networks)

[+] fiatjaf|7 years ago|reply
I love Hyperfiddle, but I'm not good enough to use it.
[+] dustingetz|7 years ago|reply
Hyperfiddle 2.0 landing soon!