This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-25
Channels
- # architecture (4)
- # bangalore-clj (3)
- # beginners (11)
- # chestnut (1)
- # cider (24)
- # cljs-dev (14)
- # clojure (97)
- # clojure-finland (1)
- # clojure-gamedev (19)
- # clojure-italy (11)
- # clojure-nl (31)
- # clojure-norway (1)
- # clojure-uk (52)
- # clojurescript (71)
- # core-async (4)
- # cursive (60)
- # datascript (8)
- # datomic (115)
- # emacs (29)
- # figwheel (11)
- # fulcro (3)
- # garden (1)
- # hoplon (1)
- # lein-figwheel (1)
- # leiningen (7)
- # luminus (13)
- # mount (1)
- # off-topic (51)
- # onyx (31)
- # pedestal (2)
- # portkey (1)
- # re-frame (22)
- # reagent (22)
- # reitit (6)
- # remote-jobs (1)
- # schema (1)
- # shadow-cljs (73)
- # specter (2)
- # sql (1)
- # unrepl (3)
- # vim (11)
- # yada (4)
I find reading from npm
ClojureScript directly a boon. It really improved my lumo
workflow and I would like to propose it for inclusion to core as well. I wrote an article some time ago about it: https://andrearichiardi.com/blog/posts/lumo-npm-dependencies.html. It was originally discussed by Antonio and I here: https://github.com/anmonteiro/lumo/issues/130#issuecomment-330083804. I wonder what David and other folks think.
I'm very happy to announce that Clojurists Together is funding @mfikes to work on ClojureScript: https://www.clojuriststogether.org/news/q2-2018-funding-announcement/
Awesome
@mfikes if you make any good jira filters, let me know and I can make them public I think
I believe that stuff is locked down pretty far right now
I've been relying on this one https://dev.clojure.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10706
I'm very excited about this!