This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-11
Channels
- # aleph (38)
- # announcements (6)
- # aws (1)
- # beginners (47)
- # calva (21)
- # cider (47)
- # cljs-dev (18)
- # clojure (40)
- # clojure-europe (7)
- # clojure-india (2)
- # clojure-italy (9)
- # clojure-nl (11)
- # clojure-norway (2)
- # clojure-sanfrancisco (1)
- # clojure-spec (17)
- # clojure-sweden (2)
- # clojure-uk (73)
- # clojurescript (10)
- # cursive (6)
- # datascript (12)
- # datavis (2)
- # defnpodcast (1)
- # duct (5)
- # emacs (36)
- # figwheel (2)
- # figwheel-main (10)
- # juxt (12)
- # leiningen (1)
- # midje (1)
- # nrepl (9)
- # off-topic (25)
- # pedestal (3)
- # portkey (3)
- # quil (2)
- # re-frame (45)
- # reagent (1)
- # ring (3)
- # ring-swagger (36)
- # rum (1)
- # shadow-cljs (48)
- # spacemacs (1)
- # speculative (50)
- # testing (2)
- # tools-deps (27)
- # yada (4)
How would I go about learning how to work with and construct real world graphs (as in graph dbs)
The question is a bit vague for me. Do you need to learn to use a graph database? To build one? A theoretical understanding of basic graph notions? A practical knowledge of common graph algorithms and data structures for use in application code?
This book, which is fantastic in general, has a terrific section on graph algorithms: http://www.algorist.com/
Welp... Kanaka did it. He went and built a lisp (mal, similar to clojure) on raw wasm: https://github.com/kanaka/mal/tree/76adfab958e24e75df358ee0c9013476dc03e95a/wasm
What does “contrib” mean, in the context of a project, language, or codebase?
Contributed by the community, usually
Community supported extensions to the core language
Thanks
In Clojure, Contrib often refers to the set of libraries under the clojure
org on GitHub, that aren't part of the core download. These have a different management/process to "regular" GitHub Clojure libraries because they're under the same Contributor License Agreement as Clojure itself.
I saw a tweet recently (I think by stu halloway?) that listed vocabulary words helpful for understanding Clojure design decisions. Somehow I can't find it again! Does anyone know what I'm talking about or have a link?
We’re going to put out some job listing soon to expand our team at work. However, I’m debating what to put up. We’re moving towards Clojure in our newer services hosted on a cloud platform but there’s still a monolithic python-django app we need to maintain until we can replace it completely. Would it be better to look for a senior Clojure dev who has some experience in other languages since it focuses on where we want to go or a senior dev with more of a general Java\Python background with an interest in Clojure to help support our legacy system?
what's the current composition of the team? Regarding their clojure expertise. I think it's good if you hire somebody with senior clojure experience that can spearhead the transition and help you pick sane things
Just me currently. I think I’m still a beginner with Clojure, especially in a production context.
Yeah you probably want a strong Clojure person with a mix of experience. Very few people have Clojure as their first language
Anyone remember Rich Hickey's codeq project? What happened to that idea? I wrote an article to spark some discussion: https://medium.com/@ustunozgur/the-nosql-database-every-software-developer-uses-10c841278a13
still very much alive :)
I expect at some point you’ll see form of codeq2
but it may be an arbitrarily long time :)
nice to hear 🙂