This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-13
Channels
- # announcements (1)
- # babashka (30)
- # beginners (43)
- # biff (24)
- # calva (72)
- # cider (12)
- # clj-commons (24)
- # clj-on-windows (10)
- # cljsrn (23)
- # clojure (123)
- # clojure-bay-area (6)
- # clojure-europe (43)
- # clojure-losangeles (2)
- # clojure-nl (2)
- # clojure-uk (9)
- # clojurescript (125)
- # core-async (9)
- # cursive (2)
- # data-science (3)
- # datomic (30)
- # devops (1)
- # emacs (13)
- # events (5)
- # fulcro (15)
- # graalvm (3)
- # gratitude (1)
- # humbleui (11)
- # lsp (5)
- # nbb (24)
- # off-topic (11)
- # pedestal (5)
- # releases (1)
- # remote-jobs (1)
- # sci (15)
- # scittle (16)
- # shadow-cljs (15)
- # sql (11)
- # tools-deps (9)
- # xtdb (5)
morning!
hello hoomins
hello fellow Europeans
I read “I just love graphics as a data structure” and my imagination ran with that for a while. 😂
the query functionality of a database, map-like semantics, and basic set operations for gluing data together. So great.
Oh, interesting @U04V5V0V4! What made you decide on Ogre?
But it’s a bit behind so I’m talking to the maintainer about helping to bring it up to date
We are looking at Neo4j at the moment... in certain cases a lot faster compared to Postgres.
@U04V5V0V4 a word of advice. Never expose gremlin to your end users. At least with the stuff we use you unleash groovy with all its powers. Which lets the user issue queries like
System.exit
Which can induce serious performance problems. So for end-user facing stuff I’d argue for making the query language an impl detail which should be kept behind an interface.
Main win is that the graph db fits the data model and make queries fast and concise in the back end
I had a dream last night. I was reading a cartoon-ish book about the history of Clojure. Several bridges were built in Colorado, and they were demolished as they weren't good enough. Finally there was the Clojuria bridge which, apparantly, was good enough. And that was what Clojure (and clojurians) were named after: the Clojuria bridge in Colorado. "Why didn't I know this earlier," I asked myself in the dream. Good morning ¯\(ツ)/¯.
-books tickets to Colorado-
The road to Cloj Durado
if you have a function that takes a single parameter, or a single parameter with some config, is your 2-arity function [x config]
or [config x]
?
with varargs I now tend to do [config & args]
, but with 2 arity I tend to do [arg config]
The reason for varargs is that it works easier with apply, but if it's fixed arity then config goes last since it's optional