This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-22
Channels
- # babashka (36)
- # beginners (42)
- # calva (6)
- # chlorine-clover (25)
- # cider (31)
- # clara (5)
- # clj-kondo (55)
- # cljdoc (3)
- # cljs-dev (7)
- # cljsrn (3)
- # clojure (73)
- # clojure-brasil (6)
- # clojure-europe (8)
- # clojure-italy (2)
- # clojure-nl (3)
- # clojure-norway (1)
- # clojure-spec (3)
- # clojure-sweden (4)
- # clojure-switzerland (2)
- # clojure-uk (29)
- # clojurescript (93)
- # conjure (21)
- # data-science (14)
- # datomic (19)
- # emacs (4)
- # exercism (3)
- # figwheel-main (38)
- # fulcro (38)
- # graalvm (42)
- # graphql (5)
- # jackdaw (3)
- # jobs (1)
- # joker (2)
- # lambdaisland (1)
- # leiningen (31)
- # malli (8)
- # meander (5)
- # off-topic (27)
- # pathom (2)
- # pedestal (28)
- # re-frame (25)
- # reagent (2)
- # reitit (11)
- # releases (3)
- # remote-jobs (1)
- # rum (1)
- # shadow-cljs (63)
- # spacemacs (17)
- # sql (1)
👋 is there something similar to Chlorine, but for VS Code, that works with a socket REPL? I asked over in #calva and was told it only works with nREPL. (I’m looking to help a teammate who uses VS Code get started working with a REPL.)
@aviflax there's an experimental version of Chlorine for vscode called "Clover"
There's yet much to be done, it's very alpha 😅
Just curious, why not call it Chlorine? I searched the VS Code “store” (or whatever they call it) and no hits came up for that name, so it seems there wouldn’t be any conflicts?
No reason, it seemed a good idea at the time to have different names :) I believe that at the time, I didn't want people to imagine that you'll have the same experience in both plug-ins, as vscode's API is harder to program that Atom.
Maybe when I can make both plug-ins have the same experience, I'll feel more comfortable in having both versions with the same name :)
I wonder if it might help findability if the “description” property of Clover in the VS Code marketplace included “Clojure”
I'll add it :). Also make some version bumps that may fix some bugs :)
The biggest difference (between Atom/Chlorine and VS Code/Clover) is the lack of programmability at startup, right? (so none of my REBL integration workflow is possible on VS Code)
Yes, and also bugs in ClojureScript, and sometimes vscode can't indent code / loses all commands on Clover without any warning, etc...
I find it strange that VS Code has so much traction, given the limitations it clearly has from a plugin/extension p.o.v. I guess it's "because Microsoft" at this point.
Yes, indeed. I believe that because these limitations, vscode feels more stable (you can crash Atom easily if your plug-in malfunctions)
For example, by benchmarking Chlorine I found that the old inline results (using Ink) was making the whole editor slower
(I’ve experienced slowdowns with Atom lately, that seem to perhaps be related to syntax highlighting of test files containing massive chunks of EDN. And I must admit I’ve been annoyed.)
@mauricio.szabo Clover worked beautifully for my teammate; we were able to accomplish our task and it was much nicer than copying-and-pasting to the terminal. Thank you!
Nice! Let me know if you find any issues 🙂
On a side note: Clover and Chlorine will probably slow down a little bit on the next 2 months... so, if you have any issues, please open a ticket, I'll probably not look at slack too much for these months.
Thanks!!! We're really happy that everything has gone well, in the middle of this worldwide confusion too. And also... she're really, really cute 😍