Not sure if this helps, but JS has array buffers, which you can use to explicitly allocate and avoid GC. As always the best documentation is on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer

Thx. I'll try to use it somehow

cljs makes use of this: https://github.com/clojure/tools.reader which looks like it should work on node.js: https://github.com/clojure/tools.reader/blob/master/src/main/cljs/cljs/tools/reader/reader_types.cljs

https://github.com/clojure/tools.reader/blob/6918abc8b3c009228790cf091097eb3037858ad6/src/main/cljs/cljs/tools/reader/reader_types.cljs#L224

Ah, great - I didn't see this

(let [promise (foo)]
  (.then promise (fn [result] ...)))

yep, all of the google closure library is available: https://google.github.io/closure-library/api/goog.html which has dom helpers https://google.github.io/closure-library/api/goog.dom.html sources: https://github.com/google/closure-library/blob/master/closure/goog/dom/dom.js

No.

You gotta restructure your code so it supports async stuff.

Huh, is there really no blocking get in core.async?

There is no blocking in CLJS, because there's no blocking in JS.

I would have expected it semantically to mean “don't move on until this form is done”

Well, you can fire off some code as a reaction to a result of a go block. Only that result->reaction part will be synchronous. But the whole app will be async - there will be other code running. That's why you can't just pass a result of a go block into a function - you have to restructure your code in such a way so that it works correctly in an inherently async environment.

thanks for the help!