This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (37)
- # babashka (28)
- # beginners (104)
- # calva (28)
- # cider (32)
- # clj-kondo (35)
- # cljs-dev (4)
- # cljsrn (3)
- # clojure (35)
- # clojure-conj (4)
- # clojure-dev (57)
- # clojure-europe (4)
- # clojure-france (6)
- # clojure-gamedev (1)
- # clojure-germany (1)
- # clojure-hamburg (2)
- # clojure-italy (7)
- # clojure-nl (4)
- # clojure-spec (9)
- # clojure-uk (11)
- # clojuredesign-podcast (2)
- # clojurescript (36)
- # clojurex (48)
- # core-async (6)
- # cursive (12)
- # data-science (1)
- # datomic (21)
- # defnpodcast (7)
- # duct (1)
- # events (1)
- # fulcro (56)
- # graalvm (30)
- # graphql (5)
- # jobs (1)
- # joker (21)
- # keechma (1)
- # leiningen (4)
- # off-topic (109)
- # parinfer (20)
- # pathom (27)
- # re-frame (4)
- # shadow-cljs (80)
- # spacemacs (18)
- # sql (32)
- # testing (2)
- # tools-deps (32)
- # vim (20)
Conjure v2.1.0 is out with support for evaluating a form at any given Neovim mark! https://asciinema.org/a/279763 This means you can evaluate things from other parts of your buffer while you work elsewhere, or even in different files and namespaces! https://github.com/Olical/conjure - intro guide https://oli.me.uk/getting-started-with-clojure-neovim-and-conjure-in-minutes/
acolyte->wizard would be better, as “idiot” literally means “person that doesn’t vote” in ancient Greek, and we don’t want to upset any ancient greeks.
Yeah, I wouldn't want to upset anyone or call anyone an idiot. A video series getting people proficient with conjure might be good though. Or more posts on my https://oli.me.uk site
Personally, I’d be very interested in the nothing-to-REPL-up-and-running scenario, as I’m entirely new to vim, neo or otherwise. Motivationally, I would find it much easier to learn vim around the REPL than to learn vim in order to get to the REPL, if you know what I mean.
Ah that's very interesting. Maybe a video series / live session for newbies would be good. Like an online follow along session for getting started from nothing with a bunch of plugins and stuff :thinking_face:
Announcing the initial public release of Clip (0.10.0). Clip is a dependency injection library akin to Integrant or Component that requires no modification to existing Clojure code. It works for both Clojure & ClojureScript, Sync & Async, Code & Data. Contributions of all kinds are welcome, at this stage design feedback is still very welcome. https://github.com/juxt/clip Discussions in #juxt
Yeah. Systems are reified, so you can def as many as you like and then start them. The concept of a system isn't a singleton.
I'd be curious to see a comparison between this and integrant / mount / component...
https://github.com/dharrigan/nextjdbc-clip is a for example for now. I need to port the rename to the example :)
@U08QZ7Y5S there's a handful of references to integrant/component in the rationale, or did you have something else in mind?
Ah, I see them now, but I missed them on a quick scan. I guess I was looking for a more direct "comparison to other libraries" section. No big deal though
That's probably a doc worth writing. I'll open an issue and tag you, if you don't get there first.
A comparison table could be killer Some points aside from the obvious: - suspendability - whether the system is reified (already addressed)
@UEM4BH7B3 Since you write
that requires no modification to existing Clojure code is the main reason for its existence refactoring legacy applications?
@U0FT7SRLP not really. Although I think it would be a great fit there. I was frustrated at constantly adapting functions into multi methods and records. If you build granular systems, it's quite frustrating, you end up with 3-line multi methods which defer to a function doing the work. I wanted to capture the ability to write idiomatic clojure code, the kind I would put in a library without hesitation, and not have to make it aware of a particular state library. One of the other benefits I was looking for was docstrings, which vars naturally support. Something I want to explore further is for personal development setups, rather than having a pre-defined dev system. Somehow tying that into minimalistic repl driven development. But that's a major WIP for me.
@UEM4BH7B3 Thanks for explaining, make sense! The introduction of async is also interesting. I'm curious how this can be applied
The async? We use async in a project to setup re-graph. But that project has a custom system, so I made a new custom system library.
Maybe I'm thinking too much from a component perspective. I'll read the documentation better
The idea is that when you return something async, dependent components won't have their start called until the async thing is resolved.
Yeah. It's on my list. Going into the JUXT website next week, so it'll probably be done in parallel
To clarify, it'll be unofficially supported in edge, but probably won't be documented until I've used it a few times and I'm happy.
Documented a comparison with other libraries https://github.com/juxt/clip#comparison-with-other-libraries feedback welcome on other tabs worth having
@U09LZR36F thanks for sharing! Just curious, what is the inspiration for the name “clip”?
New release 0.12.0 available! https://aiprobook.com/deep-learning-for-programmers?release=0.12.0&source=cslack