This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-25
Channels
- # aleph (15)
- # beginners (65)
- # boot (46)
- # chestnut (3)
- # cider (1)
- # clara (11)
- # cljs-dev (5)
- # cljsjs (4)
- # cljsrn (13)
- # clojure (180)
- # clojure-dev (2)
- # clojure-italy (10)
- # clojure-russia (62)
- # clojure-spec (6)
- # clojure-uk (85)
- # clojurescript (45)
- # community-development (11)
- # crypto (3)
- # cursive (10)
- # datomic (94)
- # defnpodcast (2)
- # fulcro (4)
- # heroku (1)
- # hoplon (4)
- # jobs (3)
- # juxt (10)
- # leiningen (1)
- # luminus (4)
- # mount (13)
- # music (1)
- # off-topic (10)
- # onyx (2)
- # portkey (15)
- # proton (2)
- # re-frame (16)
- # reagent (10)
- # shadow-cljs (194)
- # spacemacs (2)
- # specter (2)
Thanks @krauser! I'll check this out!
@rovanion what makes you think that?
Apropos his comment https://clojurians.slack.com/archives/C0E1SN0NM/p1506195162000043
ah.. I'd interpret that more as "let's all help fix re-natal issues" 🙂
@drapanjanas does a great job maintaining it IMO
there's a lot of room for improvement of course but re-natal is very usable at this point and up-to-date with react-native
@rovanion I don't know of a better solution than re-natal right now, so you should definitely use it. As @pesterhazy said, I'm more focused on raising attention about re-natals issues so we can all improve it more.
Multiple design issues are have caused us to insert workarounds in both our workflow and our source code.
@jeaye can you give an example? I'm curious