This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (23)
- # beginners (7)
- # boot (6)
- # clara (1)
- # cljs-dev (2)
- # clojure (89)
- # clojure-argentina (1)
- # clojure-australia (5)
- # clojure-brasil (4)
- # clojure-denmark (2)
- # clojure-france (1)
- # clojure-italy (1)
- # clojure-japan (9)
- # clojure-nl (13)
- # clojure-russia (1)
- # clojurescript (248)
- # clojurex (3)
- # clojutre (3)
- # core-async (2)
- # datomic (6)
- # devcards (19)
- # devops (1)
- # events (1)
- # funcool (9)
- # hoplon (74)
- # ldnclj (53)
- # melbourne (3)
- # off-topic (25)
- # onyx (36)
- # reagent (8)
@jonpither: @malcolmsparks nice talks last night. I always enjoy talks that don’t assume months of previous knowledge or a higher degree in CS! Particularly enjoyed the impromptu Emacs education moment from Bodil.
@otfrom: @mccraigmccraig I’d be interested in why re-frame too. I struggled to get to grips with Om and I’m finding it easier to understand reagent (haven’t looked at re-frame on top yet other than @malcolmsparks talk last night). Pro’s and Cons Om/Reagent/Re-frame ?
I think with Om, on the plus side, there's some value in staying with the official, mainstream incumbent. After the JS land of frameworks coming and going, it can be a good option to stay out of the churn-lane.
That said, if Reframe takes center stage and simply takes over as the prominent choice, then all the better. Kind of interested to see about Om Next though before we can declare Om is outdated.
I forgot to show last night that in fuzz there's a demo of Server Sent Events, from the REPL you can send a msg to ClojureScript, that gets sent on to Slack
quiescent as i am a noob to this reactive stuff i rather quote magnars:
> it's got a nice data-centric API. Feels very functional and clojure-like, unlike Om. […] has such a great approach to component local state.
but feels like almost too many choices so I guess @jonpither has a point too
@agile_geek: @jonpither piece of elisp i use for toggling font size
(defun toggle-font-height () (interactive) (let ((font-height (face-attribute 'default :height))) (if (= 130 font-height) (set-face-attribute 'default nil :height 180) (set-face-attribute 'default nil :height 130))))
the thing i like about re-frame is it's simplicity... both in it's implementation and use. the impl is tiny, and in use it's obvious where to put everything... it's easy and fun and i've spent time building function rather than figuring out how the framework works, or rsther, doesn't. that said, i agree with @jonpither that it might be premature to announce the demise of om before seeing om/next
@benedek: Thanks for that. Adding it to my init.el today. 😁
@agile_geek: no worries
@otfrom is that a “I’m half asleep Good Morning” or did you fall asleep on your keyboard….again?
it's running on a free dyno on heroku so sometimes it's asleep and it'll take about 30 seconds to wake up
always fun when people reply to the lndclj jobs list and they think it is only going to go to the author...
I emailed him and asked him if he wanted me to reject the post. He said yes, so I did.
reminds me of when one time we got an email regarding an office move.... and someone hit reply all saying "I don't want to sit next to XXXX".... oops
@agile_geek, @jonpither: to touch on the re-frame vs Om topic, i’ve been working with Om and have had to come up with an architecture around it for larger apps to basically keep a separation of concerns and modularity, and that just happened to be a pub/sub event driven setup using core.async, after looking at re-frame i found it to be a very similar architecture, yet more elegant which I partially attribute to not having to deal with passing cursors and the verbosity of ref-cursors around (usually through the shared state Om provides). I plan on trying out re-frame by porting my app to it to see if it actually solves those pain points and/or introduces its own.
Adds soo much flexibility, without having everything go through the single app state
First draft of the blog post that describes my technique for isomorphic clojurescript done. It’s 3620 words, probably the longest I written in quite a while
@pupeno: You’ve obviously written about another 1600 words since I talked to you last night! One for the three hour train journey home on Friday I think 😄
@agile_geek: I did. @afhammad: me neither, but it was a lot of research which I’m trying to explain.
I think we can say I officially no longer control #C0522EZ9N https://www.eventbrite.co.uk/e/september-canary-wharf-clojurians-monthly-dojo-tickets-18093404861
@otfrom: Well Dr Frankenstein? How does it feel to have created a monster?