This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-12
Channels
- # adventofcode (6)
- # announcements (10)
- # beginners (70)
- # boot (55)
- # calva (15)
- # cljs-dev (18)
- # clojure (32)
- # clojure-europe (4)
- # clojure-nl (2)
- # clojure-spec (20)
- # clojure-uk (6)
- # clojurescript (14)
- # cursive (11)
- # datomic (31)
- # figwheel-main (7)
- # fulcro (1)
- # incanter (1)
- # jobs-discuss (3)
- # juxt (1)
- # off-topic (17)
- # onyx (5)
- # pathom (3)
- # pedestal (2)
- # quil (20)
- # re-frame (6)
- # reitit (1)
- # ring (2)
- # rum (5)
- # shadow-cljs (73)
- # spacemacs (5)
- # tools-deps (11)
- # uncomplicate (1)
- # unrepl (1)
- # yada (11)
I recently met with @alandipert and @micha to talk about the future of boot. I will be officially taking over as maintainer, you can read about it here: https://medium.com/degree9/boot-future-boot-e1948562d8d3
You can also now buy your official boot-clj swag over at http://OpenSwag.co https://openswag.co/products/boot-clj-mug
@flyboarder thanks for taking over. is there any public information about why the original maintainers step down?
@borkdude i don't use boot (or clojure) professionally anymore and micha is devoting his OSS energies to hoplon
we still plan on meeting with matt monthly to help him triage/ideate/deploy or however else he needs our help with
so, we'll still be involved with the project
@alandipert makes a lot of sense. what do you use now, I saw some R related tweets coming by
i work on dev tools for R at rstudio, makers of the IDE
thanks it's been really fun to work on!
and yeah, R is also really fun. lispy, even
neat, yeah data science definitely lends to R
@jayzawrotny usually something like
boot pom jar install
Boot reminds me of gulp for js, which I loved. Composing pipelines is a great idea to me. However, boot has more jobs to do for clojure that kinda overlap with what npm does for node.
gulp, at least the last time i looked at it (a few years ago) has the issue that the pipeline isn't working on data passed from one step to the next -- the steps are working on a big mutable tree of files
I thought broccoli uses the trees and gulp uses streams to work on vinyl file wrappers?
That makes sense. I think gulp was intended to work that way but itโs difficult to enforce gulp.src('**/*.scss').pipe(sass.compile()).pipe(gulp.dest('./public'));
where steps in the pipeline are only supposed to operate on data flowing in and push data out.
boot tasks receive a "fileset", do some work to the files in that fileset, and then create a new immutable fileset they pass to the next task
each task in the pipeline gets the HEAD, adds their own commit, and passes the new HEAD to the next task
Is the new fileset given to the second task based on the first task fileset or completely separate?
For a more specific use case Iโm working on some cljs lein templates and the repo is lein based but I would like to have some tasks while developing the template for deploying and updating versions in README. Does it make sense to throw boot into the template project for that?