Fork me on GitHub
#chlorine
<
2020-06-22
>
aviflax15:06:23

👋 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.)

mauricio.szabo15:06:31

@aviflax there's an experimental version of Chlorine for vscode called "Clover"

aviflax15:06:43

ah cool, I’ll check it out — thanks!

mauricio.szabo15:06:57

There's yet much to be done, it's very alpha 😅

aviflax15:06:31

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?

mauricio.szabo15:06:28

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.

mauricio.szabo15:06:27

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 :)

aviflax15:06:29

Makes sense!

aviflax15:06:14

I wonder if it might help findability if the “description” property of Clover in the VS Code marketplace included “Clojure”

mauricio.szabo15:06:31

I'll add it :). Also make some version bumps that may fix some bugs :)

seancorfield16:06:26

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)

mauricio.szabo16:06:26

Yes, and also bugs in ClojureScript, and sometimes vscode can't indent code / loses all commands on Clover without any warning, etc...

mauricio.szabo16:06:02

And there's no inline results because vscode does not support :)

seancorfield16:06:25

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.

mauricio.szabo16:06:52

Yes, indeed. I believe that because these limitations, vscode feels more stable (you can crash Atom easily if your plug-in malfunctions)

mauricio.szabo17:06:45

For example, by benchmarking Chlorine I found that the old inline results (using Ink) was making the whole editor slower

aviflax17:06:54

VS Code also has a reputation of being fast

aviflax17:06:02

(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.)

aviflax17:06:59

@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!

mauricio.szabo18:06:49

Nice! Let me know if you find any issues 🙂

mauricio.szabo18:06:10

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.

mauricio.szabo18:06:24

The reasons is that I'm a dad now 🎉

aviflax13:06:10

Fantastic! Congratulations!

mauricio.szabo00:06:21

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 😍

aviflax00:06:01

OMG adorbs!