This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (27)
- # beginners (17)
- # boot (216)
- # cider (13)
- # cljs-dev (4)
- # clojure (103)
- # clojure-berlin (2)
- # clojure-dev (18)
- # clojure-italy (14)
- # clojure-japan (1)
- # clojure-nl (4)
- # clojure-norway (1)
- # clojure-russia (8)
- # clojurescript (291)
- # clojurex (12)
- # datomic (31)
- # editors (1)
- # events (16)
- # hoplon (60)
- # jobs (1)
- # ldnclj (85)
- # luminus (15)
- # onyx (2)
- # re-frame (18)
- # reagent (36)
- # remote-jobs (3)
- # yada (3)
re: that whatsapp article, as joe said on twitter it was only 13 erlang engineers, all the rest of them were for ios and android apps
Don't think I've ever heard about a project with lower engineer-to-user ratio than whatsapp, pretty damn impressive.
@luposlip: currently working (as contractor) on one dynamic Java web app in a large enterprise that has 800 developers! For one app!
Right, ~13 Erlang programmers. Half of HN/Reddit remains completely unimpressed because it is “just chat"
I just release a my first Clojure library. I would love some feedback. https://github.com/LockedOn/graph-router
I've been looking fo something like that. Is there any graphQL in Clojure yet ? Or is it something that we don't want ?
Closest CLojurelandhas to graphql is I think what this guy had been exploring in his last couple of posts - http://hueypetersen.com/
As for whether that's something desirable or not, I'd hazard a guess it is since Om.next seems to be moving into that direction.
That would be awesome ! I was under the impression that it was undecided between Falcor / GraphQL though ?
I use Reagent rather than om so I'm not that up to date, though I was under impression it was something custom, just inspired by those libraries.
I use neither yet (but it will probably be Om). Well they made pretty good choices so far so ... let's see
I'll probably stay with Reagent (and/or move to Rum, Reagent seems to make it hard to interface with Datascript properly) and write something similar myself (half because I want to, half because I have to because I made that my thesis project).
From what I've used of Reagent it seems to make it hard to hook into it's atom dispose protocol (or maybe I'm just missing something) while Rum makes things like that explicit, which makes the former not so nice integrating with Datascript, and the latter considerable better (which I guess makes sense, since it's by the same author and it was one of the motivations I think).
yes so it would potentially mean better integration with any storage engine ? You just made me reconsider learning Om. Maybe just first then as it has probably a better documentation for now
I'm not saying om is bad (I'm just kinda put off by how spartan it appears with all that reify and #js and non-clojurish-casing, but that's really personal and maybe it's my failing for not getting past that) it just that Reagent seems more pleasant for starters.