Fork me on GitHub
#fulcro
<
2020-09-06
>
sihingkk00:09:14

hi, had anyone experience with using fulcro+pathom together with neo4j (or any other graph db? )

lgessler01:09:46

copy pasting what i wrote krzysztof here:

lgessler01:09:42

wasn't too bad, the worst part i'd say is that neo4j's identifier syntax isn't really compatible with clojure keywords (so my neo4j nodes would look like `(p:Person {address: ..., ...})` but I'd have to write code to turn that into `{:person/address ...}`). not the end of the world, but you need to either accept that you'll be putting functions in to deal with renaming variables everywhere, or you need to write a macro to do it for you you can see here for the code i wrote: https://github.com/lgessler/glam/blob/605b09f462079afa81a68b69c4de6747c3a6da49/src/main/glam/models/project.clj i think if i had kept going with neo4j i would have looked hard for a way to make the interop stuff less painful hope that helps, let me know if you have more questions

xceno20:09:20

I'm currently building a system with fulcro + pathom and use datomic as a graph db. Ping me in some month and ask me how it went. But right now (2 months in), I'm quite impressed. I was considering neo4j but datomic just made more sense to me at the time

holyjak07:09:43

I struggle with long recompilation times of 3-7s shadow-cljs in my Fulcro app. I have tried RAD demo and it has a similar though smaller problem. Do you have similar experiences? (I have 4y old macbook pro). Wilker reported: > 3-7 seconds seems a very high time for me, in the biggest project I worked on (30k+ LOC), we were still getting compilations in 500ms avg (except when touching some of the big files, there it could go up to 3 seconds, but rarely more than that)

tony.kay18:09:50

@holyjak are you talking about initial startup full compile, or incremental compile on save? Incremental compiles on my late-2013 macbook pro are sub-second on 30kloc projects (of mine). That said, you can make your compile times really horrible if you use large namespaces. Part of the reason Fulcro is split into so many nses is this keeps compile times low. every time you add a function to a file you increase the probability that you’ll edit that file, and you also increase the liklihood that you’ll require it in other files. Editing that file will trigger recompiles of that file and anything that requires it. So: • Keep nses small • Prune your requires aggressively. Don’t leave unused requires in a file. Closure will (mostly) DCE them on adv builds, but they will hurt your incremental times

❤️ 3
tony.kay18:09:26

Put 30kloc in one file and pretty much expect super long compiles, because there is no incremental to that…it has to do the ns from top to bottom.

tony.kay18:09:41

Editing dashboard.cljc on f-rad-demo for me: initial compile 16s, first incremental 0.58s next 0.49s. Editing sales_report.cljc: 0.565, 0.551, etc

tony.kay18:09:02

that is on my desktop, which is a little faster than that old laptop, but not more than abt 30%

tony.kay18:09:22

of course both machines have SSDs and sufficient RAM, which matters

holyjak11:09:42

Thanks a lot! I have an early 2015 MacBook Pro with 16GB RAM (14GB used) and an SSD disk, which was a high-performance machine at that time but perhaps is too aged now. The OS complained about the disk being used but increasing the free space from 5 to 10GB did not change the performance.

lgessler23:09:40

if a component is a dynamic router's target and it has :initial-state, should the router be passing its initial state to it? i thought the answer would be yes but i can't seem to get it to work