This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-09
Channels
- # admin-announcements (1)
- # beginners (78)
- # boot (36)
- # cider (13)
- # cljs-dev (15)
- # cljsjs (3)
- # cljsrn (10)
- # clojure (99)
- # clojure-austin (1)
- # clojure-australia (1)
- # clojure-italy (14)
- # clojure-korea (17)
- # clojure-norway (1)
- # clojure-russia (42)
- # clojure-sg (1)
- # clojure-spec (50)
- # clojure-uk (80)
- # clojurebridge (24)
- # clojurescript (83)
- # community-development (10)
- # conf-proposals (36)
- # core-async (12)
- # cursive (20)
- # datomic (38)
- # hoplon (63)
- # lambdaisland (2)
- # leiningen (6)
- # nyc (2)
- # om (54)
- # om-next (52)
- # onyx (129)
- # planck (15)
- # re-frame (38)
- # reagent (2)
- # rethinkdb (8)
- # specter (1)
- # untangled (2)
@xcthulhu unlikely we’ll do anything about the IO problem anytime soon - too low priority for now
I've been struggling a lot lately with dealing with crypto.subtle
and the fact that it's entire API is specified in terms of promises, which have scattershot support amongst the different JS platforms.
And every polyfill seems to make some assumption or another that breaks some platform.
So my proposal is to beg @pat and @mfikes to agree on an API that works for Planck, Node.js, and maybe PhantomJS, and make it a clojure-contrib thing
I suspect it doesn’t really need to be an “official" thing for now - better to just try something and see what works and what the challenges are - I’m definitely interested in following along
Okay. I think another valuable component would be to be able to check the GPG signatures on artifacts pulled down from Clojars, which is closer to my expertise.
@xcthulhu there was some discussion around this on the #boot channel as well, maybe it can be a coordinated effort to have checks on pulled jars (they are already signed I think)