This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-06
Channels
- # admin-announcements (1)
- # announcements (32)
- # babashka (38)
- # beginners (91)
- # braveandtrue (1)
- # calva (1)
- # cider (9)
- # cljsrn (19)
- # clojure (129)
- # clojure-bay-area (3)
- # clojure-europe (24)
- # clojure-italy (1)
- # clojure-losangeles (1)
- # clojure-nl (2)
- # clojure-spec (10)
- # clojure-uk (24)
- # clojurescript (14)
- # community-development (7)
- # conjure (16)
- # cursive (3)
- # datomic (20)
- # defnpodcast (4)
- # emacs (11)
- # figwheel (2)
- # fulcro (5)
- # helix (6)
- # integrant (3)
- # jackdaw (5)
- # java (6)
- # jobs (1)
- # kaocha (13)
- # lsp (8)
- # malli (29)
- # meander (2)
- # off-topic (120)
- # pathom (3)
- # podcasts-discuss (6)
- # portal (6)
- # re-frame (27)
- # reagent (5)
- # releases (4)
- # remote-jobs (6)
- # rewrite-clj (9)
- # shadow-cljs (108)
- # xtdb (5)
To be fair, both Spec 1 and Spec 2 have “alpha” all over them, but Spec 1 is solid and has been in heavy production use for a lot of people for years at this point. But the lack of an artifact to depend on for Spec 2 — that should be a hint 🙂
mutter, mutter, git deps, mutter Yes, I know 😐
removing the .alpha suffix would break a lot of programs. is this ever going to happen? ;)
I could see a sudden swift of everyone moving to 1.11 if that did happen and that might be a good thing. Then we could also starting using the new kwargs stuff.
@borkdude My understanding is that Spec 1 will stay around as-is (with .alpha
) and Spec 2 will eventually become the “core” non-alpha version when it is ready.
So folks won’t need to change their code, unless they want to move to Spec 2 (or start using Spec 2 alongside Spec 1 — which is probably what we’ll do).
Kinda depends on who it is calling a thing alpha, and the thing.
We’ve run alpha builds of Clojure itself in production since 2011 🙂