This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aleph (7)
- # announcements (3)
- # babashka (29)
- # beginners (70)
- # calva (5)
- # cider (14)
- # clara (3)
- # clj-kondo (25)
- # cljs-dev (2)
- # clojure (237)
- # clojure-conj (3)
- # clojure-europe (6)
- # clojure-italy (14)
- # clojure-nl (4)
- # clojure-uk (40)
- # clojurescript (29)
- # clojurex (1)
- # code-reviews (2)
- # cursive (3)
- # datascript (1)
- # fulcro (11)
- # graalvm (4)
- # graphql (12)
- # jackdaw (1)
- # jobs (1)
- # joker (22)
- # london-clojurians (1)
- # off-topic (132)
- # re-frame (38)
- # rewrite-clj (11)
- # shadow-cljs (200)
- # spacemacs (1)
- # sql (67)
- # tools-deps (15)
Great to see re:Clojure tweets this morning, well done and a thank you from me for those who put it together. Nice work!
I'm registered. Thank you!
Does that mean that you’ll be speaking at it @jasonbell? 🙂
@dotemacs I’m not speaking at it, I can’t go around spoiling everything now can I.
Thank you @U054W022G that’s very kind. I’m pretty up to the eyeballs with finishing the book off and work so less travel is more favourable. I’ll be cheering from home though!
@dotemacs We also need to do a patch upgrade on @thomas heckle library as well. The random seed wasn’t that random as expected 😉
Indeed great work regarding #reclojure, just registered myself 🙂 Thanks to everyone involved!
how many clojure devs are you up to now, @maleghast?
3-4 depending on how you count them, but we are still hiring... We have an offer out to one that would make us 4-5 and we are interviewing for another... This also lumps ClojureScript and Clojure developers together as well
@maleghast we don't silo on clj vs cljs - everyone gets to work on everything
Yeah, we don't in theory and I view us as all Engineers, but in the short term we are silo-ing a little to play to people's strengths
Over time I want to make sure that we don't, which is one of the main reasons for doubling down on ClojureScript.
if you aren't using shadow already for your cljs compile, i'd recommend switching
you will really want it when bootstrap time becomes an issue, which it will with any mobile app
My experience with cljs has been much better when using shadow-cljs than with figwheel… What reasons are there are to use figwheel in preference to shadow?
(although, I think there's still some work in-progress with Conjure (for Vim) for integration with shadow-cljs)
Do you have figwheel integration with vim?
It's more evaluation of buffers etc...I guess I could use shadow-cljs to do the reloading etc.. achieves the same result.
Blocker for shadow-cljs is that the prepl implementation isn't quite right. After that's sorted Conjure should work as it does with any ClojureScript prepl. (just for clarification :D)