Clojurians
#cljs-dev
<
2016-09-09
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

dnolen13:09:12

@xcthulhu unlikely we’ll do anything about the IO problem anytime soon - too low priority for now

dnolen13:09:02

there’s also the cultural problem that IO in JS is async, in JVM sync

xcthulhu13:09:44

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.

xcthulhu13:09:12

And every polyfill seems to make some assumption or another that breaks some platform.

dnolen13:09:35

yes typical JavaScript

dnolen13:09:48

this is why we back away from all these kinds of decisions

dnolen13:09:02

so while bootstrapped is a bit tedious - it actually works everywhere

dnolen13:09:10

since we don’t make any assumptions at all

xcthulhu13:09:44

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

dnolen13:09:10

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

xcthulhu13:09:42

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.

richiardiandrea18:09:17

@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)