Thomas Heller

Well that `extend-protocol` usually exists so that printing any React element in the REPL doesn't blow up. If you don't have a REPL anyways you can safely remove it. Or...

Yikes, yeah thats a lot of schema/spec. `defrecord`s themselves don't generate much code but schema code I guess can get huge. If you only use your schema relating things during...

This is with the same version of cljs/closure? `:advanced` itself is single threaded yeah. Compiling CLJS should be using multiple threads and the verbose output confirms that it does. Technically...

Would you mind running a `release` build again with `--verbose` and version `2.16.8`? I added a timer for the `ReplaceCLJSConstants` pass which is pretty much the only difference happening in...

I'm also very curious about the code in `sx/cljc/qna/schema.cljc` given that is produces 2mb of JS out of 54,1 KB source when `cljs.core` produces 1.3mb out of 339,1 KB? I'm...

> Optimizing CLJS Constants took 671ms This is indeed much longer than expected, but given the build size still reasonable. Also still fast enough to still not know where the...

@p-himik note that the Inspect UI uses `datafy`. so if you are working with a lot of custom JS classes you can extend the relevant protocols do display them in...

The problem is that the current build state is currently constructed by listening to the event stream which receives the `:build-start`, `:build-complete` messages etc. This is currently not stored anywhere...

The UI build is currently in a bit of a messy state given how experimental everything arround it is. `master` has the fix for the above issue and I added...

How many of these do you have? A little duplication is not a problem and does not warrant complicating the implementation too much. I'm not a fan of using a...