Fork me on GitHub
#clojure-uk
<
2019-11-13
>
dharrigan06:11:44

A good thing is hard to put down 🙂

dharrigan06:11:21

Morning y'all!

jasonbell07:11:29

Great to see re:Clojure tweets this morning, well done and a thank you from me for those who put it together. Nice work!

paulspencerwilliams07:11:23

I'm registered. Thank you!

dotemacs08:11:41

Does that mean that you’ll be speaking at it @jasonbell? 🙂

jasonbell08:11:29

@dotemacs I’m not speaking at it, I can’t go around spoiling everything now can I.

🙂 8
reborg10:11:59

But if you change your mind… let me know :)

jasonbell14:11:14

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!

reborg14:11:44

Fair enough, next conference you can present the book!

jasonbell16:11:41

I’m happy to stand there for 40 minutes, holding up a book, less slides to do! 🙂

jasonbell08:11:50

@dotemacs We also need to do a patch upgrade on @thomas heckle library as well. The random seed wasn’t that random as expected 😉

😀 12
thomas09:11:15

morning....

thomas09:11:37

Patching...

👍 4
guy09:11:15

Morning all!

gcaban09:11:18

Indeed great work regarding #reclojure, just registered myself 🙂 Thanks to everyone involved!

maleghast12:11:00

I am going to try and get my team to attend en masse.

Ben Hammond12:11:39

how many clojure devs are you up to now, @maleghast?

maleghast14:11:00

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

mccraigmccraig14:11:34

@maleghast we don't silo on clj vs cljs - everyone gets to work on everything

maleghast14:11:36

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

maleghast14:11:56

Over time I want to make sure that we don't, which is one of the main reasons for doubling down on ClojureScript.

mccraigmccraig14:11:00

if you aren't using shadow already for your cljs compile, i'd recommend switching

💯 8
mccraigmccraig14:11:36

you will really want it when bootstrap time becomes an issue, which it will with any mobile app

dharrigan15:11:27

I've been playing with ClojureScript recently, I'm seriously impressed

dharrigan15:11:44

Using reagent with figwheel

👍 4
rickmoynihan15:11:29

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?

dharrigan15:11:53

For me - no reasons, it's the first thing that jumped out when I did a duckie search

dharrigan15:11:35

(although, I think there's still some work in-progress with Conjure (for Vim) for integration with shadow-cljs)

rickmoynihan16:11:48

Do you have figwheel integration with vim?

dharrigan16:11:05

It's more evaluation of buffers etc...I guess I could use shadow-cljs to do the reloading etc.. achieves the same result.

Olical16:11:23

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)

dharrigan16:11:01

Yup, looking forward to that! 🙂

dominicm17:11:30

Figwheel has an api

dominicm17:11:35

Shadow doesn't

dominicm17:11:13

You have to use the cli, which means you can't e.g. Use a config system with it

dominicm17:11:37

Well, there's an api, but it doesn't take data, it reads a edn file directly.