This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-30
Channels
- # admin-announcements (1)
- # announcements (1)
- # babashka (8)
- # bristol-clojurians (1)
- # calva (36)
- # clojure (115)
- # clojure-europe (5)
- # clojure-italy (4)
- # clojure-nl (3)
- # clojure-norway (3)
- # clojure-uk (161)
- # clojuredesign-podcast (3)
- # clojurescript (71)
- # core-async (34)
- # cursive (26)
- # datomic (43)
- # docker (2)
- # emacs (24)
- # figwheel-main (1)
- # fulcro (36)
- # graalvm (7)
- # immutant (2)
- # jackdaw (1)
- # jobs (2)
- # leiningen (8)
- # luminus (5)
- # off-topic (29)
- # onyx (1)
- # other-languages (5)
- # pathom (6)
- # pedestal (3)
- # reagent (11)
- # ring (8)
- # shadow-cljs (42)
- # spacemacs (17)
- # specter (6)
- # tools-deps (80)
- # videos (1)
does anyone have notes / slides or other materials from @chrisoakman's conj 2018 unsession on tree-sitter (https://github.com/clojureconj/clojureconj2018/wiki/Unsessions#better-syntax-highlighting-with-tree-sitter) ? also, if there's already a channel where tree-sitter-ish stuff might be on-topic, please suggest 🙂
there was a strange loop talk about it
thanks, i've seen that one and iiuc oakmac's unsession may have specifically discussed his efforts on tree-sitter-clojure, which max's talk predates :)
I've been starting to think about a data "query language" for time series to allow clients to request subsets of timeseries and calculations to be run on them. No idea if this is good or not. Any thoughts (while I keep thinking about this/experimenting) would be appreciated: https://gist.github.com/jjttjj/e63ba5a366961c314b40118edc548aed
Can't really say anything about the need for such a language or the language presented in the example itself, but I'd warn against using any metadata that's not truly necessary. It's very easy to lose it and have a hard time debugging the issue.
Hello. I woud like to know wich clojure books would be good to have.
Could some folks gives me some indications?
I loved "clojure for the brave and true". "Joy of clojure" is really good also but more advanced
I liked the brave one as well!
Not really about clojure (but Scheme) but more about programming in general: Structure and Interpretation of computer programs.
Thanks
@ramon.rios "all of them" -- I know that's not helpful but...
Clojure Programming is good but quite dated. I'd recommend Programming Clojure these days instead. Also Clojure Applied. And Getting Clojure and/or Living Clojure depending on where you are in your journey.
Did you get a chance to look at the Brave and True book? Or do you not recommend it? I found it to be very good for beginners and maybe a little more experienced as well.
Lots of people love the Brave and True book. I don't like the style of it, but that's subjective. And by the time it appeared, I'd been doing Clojure in production for almost four years so it wasn't really aimed at me. Also, I had switched from Emacs to Atom by that point I think so none of the Emacs stuff in B&T -- which is a whole section early on, I believe? -- wasn't relevant either.
(and I don't actually think people should try to learn both Emacs and Clojure at the same time!)
I agree, learning both can be overwhelming. Fortunately, I was familiar with Emacs already and CIDER's debugger is amazing.
Meh, I don't like debuggers (and I never seem to need them). I don't think I've used a debugger much since I last used C++...
(and I kind of grew up on Emacs decades ago, back when it was version 17/18 🙂 )
Nowadays I use Calva which lacks a debugger. But when I started, CIDER really helped me understand what's happening. I used to trip a lot on sequences, like accidentally creating sequence of sequences instead of a flat, reducible sequence.
I tend to build code up in small pieces via the REPL -- usually in a Rich Comment Form and evaling each form as I edit -- so errors like that would be caught early on, before I had an entire function that was being called.
@ramon.rios I am probably barely past the beginner stage and I mostly keep ClojureDocs open in one tab and use the source links liberally. The best documentation is always the source!
What's wonderful about Clojure is, the code is VERY readable. It can be cryptic, but hey, it's 10 times less code. I would rather read 10 lines of complex code than 100 lines of easy code.
Don't believe me? Open markdown-clj in one tab and flexmark-java in another. Which one do you get first?
Re: docs and source -- the REPL can show you the docstring and source of any function and most editors have integrations for "view docs" and "view source" so I use those liberally while I'm coding (`ctrl-; d` and ctrl-; S respectively with Atom/Chlorine and my keymap from my atom-chlorine-setup repo).