This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-09
Channels
- # announcements (12)
- # beginners (159)
- # boot (3)
- # calva (41)
- # cider (48)
- # clara (2)
- # clj-kondo (8)
- # cljdoc (8)
- # clojure (70)
- # clojure-dev (10)
- # clojure-europe (2)
- # clojure-losangeles (1)
- # clojure-nl (12)
- # clojure-spec (7)
- # clojure-uk (63)
- # clojurescript (24)
- # cursive (24)
- # datomic (22)
- # expound (17)
- # figwheel (1)
- # fulcro (176)
- # graphql (23)
- # jobs (9)
- # jobs-discuss (56)
- # kaocha (1)
- # mount (3)
- # nyc (1)
- # off-topic (91)
- # onyx (3)
- # overtone (4)
- # pathom (3)
- # pedestal (1)
- # re-frame (11)
- # reitit (19)
- # ring (8)
- # shadow-cljs (16)
- # test-check (5)
- # testing (2)
- # tools-deps (20)
- # vim (9)
We've recently published corallo
, a tiny graph library in Clojure. It's available on Clojars too. https://github.com/7bridges-eu/corallo
Congrats! A short tl;dr a.k.a. Rationale would be helpful imho, this is just a feedback, no expectation or obligation. 😉
also comparison with another graph libraries will help a lot. [ubergraph](https://github.com/Engelberg/ubergraph) as example
cool!
yeah, I’m curious why ubergraph/loom wasn’t used. I think both those libs could use some cleanup and should be merged, but they do work. and “because we wanted the experience of building a graph library” is a perfectly good reason 🙂
@UCF779XFS There are some reasons not to merge loom and ubergraph, IIRC from having talked with @U0518RMLD.
don’t want to go too offtopic of this thread, but I would be interested in hearing reasons/plans for future of graph libs on clojure. loom has essentially been (all but?) abandoned with many outstanding issues and no responses from the devs. ubergraph seems to be a better model. it might be that “merging” just meant ubergraph replaces loom and takes ownership of the protocols and algorithms included in loom
@UCF779XFS I know we shouldn't reinvent the wheel, loom and ubergraph are awesome and far more complete than corallo. We wrote it to have something small, understandable and aimed to direct graphs (maybe we should change the description). I think corallo is more idiomatic, no protocols or any other "Javaish" stuff in its core, but pure clojure data structures. That's all.
FWIW, I consider protocols/records a very Clojuric take on Java interfaces, and think this is an appropriate application of the feature. But I concede, it's not Just Data ™️