boot

https://github.com/boot-clj/boot/blob/master/boot/base/src/m... looks like the gnu standard for C (https://www.gnu.org/prep/standards/standards.html#Formatting), applied to Java. I think that was done to make grepping for function definitions easier (when searching for the definition of foo, grep for “^foo\b”. That makes implementing “go to function definition” possible without having to parse code)

The recent discussion [1] on the Black formatter for Python had me thinking about whether there is any innovation still happening in the realm of code formatting. Most of the possible ways to format code in each language must have been tried by now, and I would expect we've converged on a narrow range of permutations purely for practical reasons. But recently I did see an interesting example [2] of Java formatting from the Boot library for Clojure, with a style that I had never seen before in that language. Are there other major variants of code formatting style still being developed out there? [1] https://news.ycombinator.com/item?id=30130315 [2] https://github.com/boot-clj/boot/blob/master/boot/base/src/main/java/boot/App.java

What's wrong with the tooling? My current CLJS setup is boot with boot-cljs, boot-reload and boot-cljs-repl. They're configured using normal Clojure code in a build.boot file and the entry points are configured in live-reloadable *.edn files. That setup is simpler and far more powerful than anything else I've seen in other languages. I was using leiningen previously but boot proved to be more powerful for less work in my case. https://github.com/boot-clj/boot https://github.com/boot-clj/boot-cljs https://github.com/adzerk-oss/boot-reload https://github.com/adzerk-oss/boot-cljs-repl

From the wiki for [Filesets](https://github.com/boot-clj/boot/wiki/Filesets) "Build workflows necessarily involve the filesystem because it's not practical to send file contents around in memory as function arguments, and because we want to be able to leverage existing JVM tooling that generally operates on things in the class path and not on in-memory data structures." so like unix pipes? What exactly is impractical about passing big values as function arguments? Isn't that how gulp works?