This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-29
Channels
- # announcements (7)
- # asami (13)
- # babashka (22)
- # beginners (52)
- # calva (95)
- # clj-kondo (14)
- # cljs-dev (7)
- # clojars (5)
- # clojure (94)
- # clojure-austin (5)
- # clojure-dev (15)
- # clojure-europe (25)
- # clojure-nl (18)
- # clojure-uk (15)
- # clojuredesign-podcast (28)
- # clojurescript (63)
- # copenhagen-clojurians (1)
- # cursive (3)
- # datalevin (7)
- # datascript (13)
- # datomic (13)
- # duct (14)
- # emacs (24)
- # events (1)
- # fulcro (13)
- # graphql (7)
- # kaocha (4)
- # lambdaisland (6)
- # lsp (22)
- # music (5)
- # off-topic (24)
- # rdf (1)
- # re-frame (3)
- # reitit (9)
- # shadow-cljs (23)
- # sql (15)
- # testing (4)
- # tools-build (6)
- # vim (7)
- # vscode (7)
- # xtdb (21)
I've been wondering if it's time to just go ahead and add clojure.spec.alpha to bb (as a built-in, rather than from source) (and nbb). It seems spec2 isn't coming any time soon.
one argument in favor of this, is that even after spec2 gets released, libraries using spec 1 will still be around for a long time (and prob some cases may never get upgraded)
@U9G5NDV4Y hehe :) My only concern with adding more stuff is longer compilation times and larger binaries but if resources grow along over time this shouldn't be a problem - but they might not (mostly thinking about CI resources)
what do you think about a "kitchen sink" bb vs the current "slim" bb or something?
But if you look at the Windows CI for example, it has 5gb memory and is already spending way too much time in garbage collection
oh wow, ok
I didn't realize that was the limit that was being hit
Another idea, having spec1 as a builtin pod. It would be packaged with babashka and the end user doesn't have to know it's a pod (have a small proxy that delegates to the pod). Downside: small extra startup time when using spec. Upside: - separate compile cycle, no extra startup time when not using spec
Spec as a pod doesn't really work well as specs contains functions and functions can't be serialized. Spec is already available as a library with babashka (fully supported), just not built-in
Ah too bad
Hehe nice
I wonder if Clojure itself is going to maintain the support for spec1 alpha (by that I mean keeping it available as a clojure built-in with the language) once spec 2 gets out, according to the "no break paradigm" it should keep existing there, I'm curious too see how that will go