This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-11
Channels
- # announcements (1)
- # architecture (23)
- # beginners (189)
- # boot (1)
- # calva (62)
- # clj-kondo (23)
- # cljs-dev (9)
- # clojure (336)
- # clojure-dev (11)
- # clojure-europe (2)
- # clojure-italy (17)
- # clojure-nl (25)
- # clojure-uk (53)
- # clojurescript (12)
- # core-async (29)
- # data-science (1)
- # emacs (6)
- # fulcro (23)
- # garden (3)
- # graphql (2)
- # jobs (1)
- # joker (7)
- # off-topic (17)
- # om (2)
- # qlkit (1)
- # reagent (15)
- # reitit (18)
- # rewrite-clj (7)
- # shadow-cljs (176)
- # sql (1)
- # test-check (4)
- # vim (32)
- # xtdb (30)
so quiet in here. Has anybody started trying to use crux in anger that isn't a juxt'er?
@hoppy hey, I haven't looked again in the last 4 weeks, but the last time I searched around on GitHub I found a few interesting things: https://github.com/mjul/crux-db-lab https://github.com/zirmite/crux-fun (just a template, by the looks of it) https://github.com/harold/docbrown ("An application for time-traveling source exploration")
I have a potential donor project that I'm giving some serious consideration to trying out on crux.
It's backing store is pure s**t, maintained for compatibilty/interop with an ancient (circa '70s) desktop app. It's sort of a CRM/ERP system, and has probably 100'ish ISAM tables.
Wow, sounds intriguing! If there's anything at all we can do to help you figure things out we're very happy to chat 🙂
I got vexxed using DT for exactly the bi-temporal issues that seem to drive crux. I have historical (log-style) data that has to be fit back in, and I have to do it piecemeal as I go.
I was pondering how to weave all this together against a TX timeline, and that made my head hurt.
@taylor.jeremydavid, are you juxtian?
I'm psyched to get into it. We've been about 3 years dragging this boat-anchor around getting to the point of being able to turn off the old system
What you described about CRM/ERP migration reminds me of some great comments I read on that "Salesforce is buying Tableau for $15.7B" HN thread.
I think we all are! I have to run now, but I looking forward to chatting again soon, and feel free to ping me if you fancy a video call sometime
so despite all the PR, I'm still unclear on one point. If I have, say a 20K document, and change one field, what does crux store, the whole thing again, or a delta?
yep it's a balancing act for sure, but we're hoping to create a subgraph decorator that will make splitting your documents apart (and accessing them again) more seamless