lowecg

Comparing GraalVM output between depstar and tools.build, the number of reachable fields has increased significantly between the two compile runs, and `clojure.core` has grown with the latter. GraalVM depstar: ```...

As a very coarse comparison between the content of the respective uber jars reveals some differences: ``` jar -ft .holy-lambda.depstar/build/output.jar | sed -E 's/([0-9]+)//g' | sort > x jar -ft...

I'm going to roll this out to a few other lambda projects. I suspect the increase in code size is from `tools.build` being more thorough.

I've applied the new build to another 6 Lambda functions and the package size inflation is negligible: 0 - 0.1MiB

> The single-segment warnings are something you should address rather than add the init options as you did. Not sure how I'd do that. `clj-tuple` and `potemkin` are transitive dependencies...

The depstar version had the following, which I can't see an alternative for in the new version. Could there be anything in that? ``` :jvm-opts ["-Dclojure.compiler.direct-linking=true" "-Dclojure.spec.skip-macros=true"]} ```

`tools.build` is more aggressive at pulling in Clojure code. In another Lambda, I had a namespace amongst my lambda code called `repl-helper.clj`. It just had some utils that I could...

I just added the original `jvm-opts` to the build alias, and the size package is back to what it was initially. ``` :aliases { :build {:deps {io.github.clojure/tools.build {:git/tag "v0.8.3" :git/sha...

@evilsneer Using the recommendations from [above](https://github.com/hodur-org/hodur-visualizer-schema/issues/10#issuecomment-733117566), the following procedure worked for me. Hopefully it gets you moving: **Create the directory structures** ``` mkdir hodur-viz cd hodur-viz mkdir -p resources/public/scripts mkdir...

Thank you for reviewing this, Oli. I was trying to be agnostic in the naming of "subscription as data", but I'm not sure if it is a common pattern so...