Clojurians Log v2

@seancorfield Maybe mention this policy in the topic then? To me this channel is a perfect place for this type of announcement (I didn't know about the other channel until now) but I'm fine with the other place if it's easy to find.

@jumar read this channel's description -- it really is pretty clear.

I know (after I read it) but it's not clear where the other things should go. Also the channel name is quite generic

The description can't be expanded -- Slack has a limit there. I've updated the topic to point to other channels.

Most people read the topic, see it's only for projects and libraries, and ask in #slack-help or #community-development about where they should post non-project/lib announcments.

BTW, channel topics are also limited in length and, unfortunately, any member can change the topic so we're always at the mercy of members changing the topic -- it's not something Admins can control...

@jumar Everyone is auto-joined to #events and #news-and-articles so I'm surprised you didn't know about them.

(also to #slack-help #beginners #clojure #off-topic -- from that initial set of seven channels, folks ought to be able to figure out how to get around here)

Thanks, that helps. I wasn't there for some reason - maybe the "auto join" for this channel was only configured after I joined clojurians? (I think more than 3 years ago)

Entirely possible -- but if you've been around that long, I'm genuinely surprised you haven't run across those channels by now... 🙂

Is there a difference from tools.trace ? https://github.com/clojure/tools.trace

@seancorfield Thanks, for letting me know, I'll use #news-and-articles in the future.

cc @daslu

@holyjak Thanks for the feedback! I can reproduce the problem, and I'll look into it.

i would say its a bit different, the aim of mate-clj is to print to repl the steps of execution of the macro/fn and to give the developer more understanding about each step and how it got to the final result.

The publicly available https://kennytilton.github.io/whoishiring/ browser (a Matrix JS app) has now been ported to CLJS Matrix: https://github.com/kennytilton/matrix/tree/master/cljs/whoshiring. Yay. Compare also with a pure CLJS Reagent https://github.com/kennytilton/matrix/tree/master/cljs/whoshiring and re-frame https://github.com/kennytilton/rehiring.

That's pretty awesome. Of course, the first thing I typed in was "clojure" 🙂

I had no idea that Cells was coming to CLJS!

@dharrigan Yep: mine is “clojure or cljs or scheme or lisp”. I’ll throw in dart and flutter just to track those.

@dj942 I gotta talk to my PR crew! 🙂 I ported Cells to CLJ/CLJS thru the awesomeness of CLJC ’bout five years ago, and instead of Qooxdoo on the front-end just went with mxWeb, a thin Cells-powered HTML wrapper. That is used in this latest whosHiring implementation. Thx for your Cells enthusiasm!

ps. If anyone wants to play with Matrix, ping me on #matrix and I will do up whatever doc you need. There are a bunch of demo apps, but they might have some bit rot. I’ll get those out of mothballs if desired.

It is a reactive hack akin to MobX, if you know that one. R/atoms have nice reactive capabilities, but last I looked suffered from glitches. Here is an old write-up. Skim down to “data integrity” for the gist. http://smuglispweeny.blogspot.com/2008/02/cells-manifesto.html

Didn’t know Cells was also here in clojure-land either, that’s awesome!

Thx, @mjcurry! Cells actually picked up a few tricks moving to a non-OO basis, including instance-specific Cells and Cell-specific observers. Same in JS, btw, and in JS with defineProperty we get the same transparency as with CLOS. In CLJ we need to access properties with md-get to engage the cells wiring. Not the end of the world.