This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-02
Channels
- # 100-days-of-code (1)
- # announcements (2)
- # beginners (122)
- # boot (5)
- # calva (5)
- # cider (54)
- # cljdoc (1)
- # clojure (132)
- # clojure-brasil (1)
- # clojure-italy (4)
- # clojure-nl (6)
- # clojure-uk (105)
- # clojurescript (43)
- # core-async (17)
- # cursive (14)
- # datomic (60)
- # emacs (35)
- # figwheel-main (44)
- # fulcro (70)
- # graphql (1)
- # jobs (19)
- # jobs-discuss (5)
- # leiningen (5)
- # luminus (2)
- # off-topic (40)
- # onyx (2)
- # overtone (5)
- # re-frame (36)
- # reagent (29)
- # ring-swagger (20)
- # rum (13)
- # shadow-cljs (19)
- # testing (5)
- # tools-deps (25)
- # vim (5)
@markx: I'm not up to date with clojureVSCode, so can't do a comparison. But the reason I made Calva was that something (I have forgotten what, maybe several things) was missing to support my workflow. But since then Calva has developed a bit faster than clojureVSCode, I think. Calva has a rich set of evaluation options, evaluating inline as well as pretty printing to the output pane and also evaluating in the (somewhat) integrated Terminal REPLs). The Terminal REPLs themselves are unique for Calva I think. For ClojureScript projects Calva makes it easy to select which REPL should back the evaluations. Also Calva has shadow-cljs
support (well, it tries to, and shadow-cljs
is part of the tool chain for developing Calva).