This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-10
Channels
- # announcements (1)
- # asami (36)
- # babashka-sci-dev (5)
- # beginners (4)
- # calva (10)
- # chlorine-clover (2)
- # clj-commons (2)
- # clojure (35)
- # clojure-android (1)
- # clojure-norway (1)
- # clojurescript (11)
- # cursive (8)
- # deps-new (5)
- # emacs (8)
- # fulcro (11)
- # graalvm (15)
- # gratitude (5)
- # holy-lambda (11)
- # jobs-discuss (5)
- # lsp (9)
- # off-topic (9)
- # other-languages (2)
- # pathom (6)
- # polylith (43)
- # portal (35)
- # quil (6)
- # react (13)
- # reclojure (3)
- # releases (5)
- # rewrite-clj (13)
- # shadow-cljs (32)
:thumbsup::skin-tone-2: https://github.com/seancorfield/deps-new/commit/22385c8ab5e79d022eddbc0be75ecd5f6bb6e0ea
> If you want an application you could just create an application in the first place? I don't follow. I wouldn't use clj-new for this?
We're talking about deps-new
and I was getting a bit cheeky, but I really meant: create a template, then create an application, and use it as a guide to modify the template. I sort of assumed anyone creating a template would always modify it, so complaining that it produced a library seemed odd to me.
People often complained that clj-new's template project wasn't useful because it was too minimal so when I made deps-new's template, I made it more complete - but figured people would still complain no matter what the default behavior was 😕