This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-02
Channels
- # aws-lambda (1)
- # beginners (46)
- # boot (190)
- # cider (12)
- # clara (6)
- # cljs-dev (9)
- # cljsjs (8)
- # clojure (152)
- # clojure-austin (3)
- # clojure-berlin (3)
- # clojure-finland (2)
- # clojure-france (5)
- # clojure-italy (3)
- # clojure-russia (92)
- # clojure-serbia (4)
- # clojure-spec (7)
- # clojure-uk (190)
- # clojurescript (115)
- # cursive (20)
- # datomic (20)
- # dirac (4)
- # emacs (9)
- # gsoc (5)
- # hoplon (1)
- # jobs (1)
- # klipse (4)
- # lein-figwheel (1)
- # leiningen (6)
- # lumo (2)
- # mount (18)
- # off-topic (57)
- # om (68)
- # om-next (14)
- # onyx (33)
- # perun (32)
- # portland-or (4)
- # re-frame (21)
- # reagent (85)
- # ring (6)
- # ring-swagger (23)
- # schema (1)
- # uncomplicate (1)
- # untangled (13)
- # vim (7)
Haha I just started making a blog @ http://ghost.org and one of the loading texts "Millions of electrons are repositioning themselves."
@qqq I learned om first like two years ago. I found it to be very complex back then and hard to understand. When I finally grasped it and used it for some toy stuff I took a look at reagent. Understanding and using it was like two orders of magnitudes easier. Whereas I would say that one order of magnitude came from the fact I learned the FRP concepts while learning OM.
@sveri which would you reach for now, having used both? I’ve mainly used Rum to date but I’m considering trying Om.Next for comparison
Same experience as @sveri here, learning FRP while learning OM and found reagent easier back then. I'm not doing a lot of Cljs those days but I'd give Om.Next another try should I have some time to experiment, I'd go to reagent for my own productivity at first though.
IMO they're not really comparable, it depends what your problems are.
@sveri Same here too, but the biggest problem I had with Om was that I started with their function DOM syntax and Reagent with Hiccup.
Om.next takes ideas from graphql, falcor, datomic... There is nothing comparable in rum, reagent, etc...
You'd look to om for the same reasons you'd look to graphql and falcor. There is not much point comparing the two as simple reactjs wrappers.
I only learned much later that you can use sablono with om to get the same hiccup syntax like reagent.
but Om had notions of managing the global state from the start, I don't think reagent had that, but I'm not sure
about sablono/hiccup, if you're interested, take a look at kioo, it's a templating library for om and reagent inspired by enlive/enfocus
I love this concept.
@danielstockton From my understanding it was about OM and not OM.next
@arnaud_bos interesting, but it looks a bit hard to infer dom structure from the code....
it might yes, and there's a whole section on troubleshooting, but in practice I've never had to troubleshoot
One more concern I have about Om and Om.next is that it is mainly David working on it, which has not that much time in total, so I possibly feature development will suffer, while reagent is very stable and useable since two years. But thats more of a soft concern and not a hard one.
Om is pretty stable also, there is more work going into things built on top of it liked compassus and untangled.
Im going to make a custom pagination which displays numbers instead of the prev - next. Is it a good idea to make the current page in the middle or for example as 3 number.
I want to know too roelof
@pesterhazy How do you make the pagination . I think I will use ez-web
@wamaral thanks, now time to experiment how to make a google layout when Im have this output :
(= (paginate (range 101) 10 5)
{:prev-seq (4 3 2 1), :next-seq (6 7 8 9 10 11),
I could use the bootstrap idea but still I have to think well how to take the right numbers out of the prev-seq and next-seq
ugh, just noticed that influxdb is already supported by metrics-clojure (edited). There goes the last hour.
@bja, are you talking about https://github.com/sjl/metrics-clojure ?
interesting. What do you use it for, if you can explain?
I monitor jvm stats, ring stats, and various app metrics (email sends, messages failed to process, time it takes to talk to various services/databases) using metrics-clojure. It has a nice json output for quick viewing in development, but it's far more useful when I can see a historical view of the metrics via grafana. So I'm sending the metrics to influxdb and viewing them in grafana.
I'm only using influxdb for app metrics right now, although considering it for another use case around user analytics for partners
@bja, that sounds quite useful
@bja we're already using riemann for various application metrics, what does metrics-clojure provide over that? Or is it just a replacement for all the in-house boilerplate we've come up with?
as far as app metrics, it doesn't give you much over using riemann or statsd directly. it has a couple handy plugins to gather jvm metrics and ring metrics for you.
@bja what's the process to start getting some JVM metrics sent to Riemann? (Essentially: what's the overhead for me)
3 lines in project.clj and something like
(instrument-jvm)
(def riemann-conn (make-riemann ....))
(def riemann-reporter (reporter riemann-conn metrics.core.default-registry ....))
(.start riemann-reporter)
instrument-jvm lives here: https://github.com/sjl/metrics-clojure/blob/master/metrics-clojure-jvm/src/metrics/jvm/core.clj riemann stuff lives here: https://github.com/sjl/metrics-clojure/blob/master/metrics-clojure-riemann/src/metrics/reporters/riemann.clj
there are some other benefits of being integrated with coda hale's metrics library in terms of common JVM library integration