This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-12
Channels
- # adventofcode (6)
- # announcements (10)
- # beginners (70)
- # boot (55)
- # calva (15)
- # cljs-dev (18)
- # clojure (32)
- # clojure-europe (4)
- # clojure-nl (2)
- # clojure-spec (20)
- # clojure-uk (6)
- # clojurescript (14)
- # cursive (11)
- # datomic (31)
- # figwheel-main (7)
- # fulcro (1)
- # incanter (1)
- # jobs-discuss (3)
- # juxt (1)
- # off-topic (17)
- # onyx (5)
- # pathom (3)
- # pedestal (2)
- # quil (20)
- # re-frame (6)
- # reitit (1)
- # ring (2)
- # rum (5)
- # shadow-cljs (73)
- # spacemacs (5)
- # tools-deps (11)
- # uncomplicate (1)
- # unrepl (1)
- # yada (11)
Hello everyone, it is great you meet you all. Our team is pretty new to Clojure / ClojureScript & Reagent / Om & Om Next and the Clojure ecosystem but as a team of Java programmers it seems like a real breath of fresh air. We are trying to brainstorm and “layout” the ideal stack for our Non-Profit. I love the idea of everything being Clojure Based however the one thing that is confusing me is the Datomic Cloud database --- It sounds awesome. It sounds as though it could get quite expensive very quickly and as a Non-Profitable, Non-Profit that is being funded by “our team” … that makes me nervous. I just don’t want to bankrupt us before we ever get started. Any suggestions, resources, success stories, horror stories would be welcomed. Thank you for your time. Coffey.
You can try to ask about Datomic on #datomic . Probably you will get better help in that topic.
This is my stack for UI https://github.com/kwladyka/form-validator-cljs/tree/doc
IMO Clojure(Script) is not something which you want to use as framework. You want to choose your small pieces. But it is my opinion. It is first tech when I feel I don’t want to use frameworks.
It is wide topic about choosing your stack. I could write too much about this for that channel 🙂
Choosing Datomic simply to be Clojure based doesn’t seem like a good idea. Also, Datomic is closed source so realistically its Clojureness to you would effectively be the same as using many other dbs that have a Clojure library/interface. I would suggest you start by looking at what db best aligns with your apps needs and existing skill sets then look at what libraries are available to you and go from there.