Clojurians Log v2

Clover shares almost 100% of Chlorine, with the exception of inline results and renderers based on node.js libraries 🙂

These 2 features are only missing in Clover because VSCode don't have the APIs that we need to support it (inline results can't render HTML, and the console tab is a webview that can't access the filesystem at all). If I could work-around these limitations, they would overlap 100%

(Did that answer your question, @mattias504? I could expand more on that if you want!)

Calva provides a lot of static features (including formatting, Paredit, and all the nice things brought in via clojure-lsp). You can use it together with Clover. The overlap is with the dynamic side of things. You can choose which one to connect to the REPL on a case by case basis. Calva even has a setting where it will hide some of its REPL UI.

Oh, I misread that - I though that the question was how Chlorine compares to Clover 😄.

Calva supports only nREPL, but supports it really well IMHO. Clover supports both nREPL and Socket-REPL, but nREPL support is subpar. Clover does try to not inject any code in your REPL, so it uses what it can detect (if you want autocomplete and don't have Compliment at the classpath, it'll use a simplified version for example). Calva does support more things out-of-the-box, and some that Clover will probably never support (like jack-in for example)

Clover does have "custom rendering" where you can customize the way you render things (see https://www.youtube.com/watch?v=_8z1r8KV9uk for an example) and you can define "custom commands" with ClojureScript too. Also, Clover only supports Shadow-CLJS for ClojureScript (for now) and it does have some interesting features at CLJS side like tap> support and automatic promise resolution (so you'll see the contents of a promise results instead of only Promise<~>).

@mattias504 For me, as a long time Atom/Chlorine user and now VS Code/Clover user, the two big "selling points" for me are: 1) the ability to connect to a plain socket REPL running in any Clojure process (we run socket REPLs in QA and production, and having the same experience with VS Code as for local dev is awesome) and 2) not needing nREPL/Orchard/stuff added to my running app (nREPL "helps" by messing with the REPL in ways I find annoying -- see the many Qs in this Slack where someone gets "weird" results in their editor via nREPL but things work "properly" with a plain REPL).

And then Chlorine/Clover let me write arbitrary commands for the editor in ClojureScript -- see my https://github.com/seancorfield/vscode-clover-setup/ for the customization I have around tap>, test running, integration with Portal and so on (the latter is mostly in my https://github.com/seancorfield/dot-clojure repo at this point).

I also use Calva, but with the nREPL UI turned off. Calva brings a lot of useful "static" stuff, via LSP/clj-kondo, better formatting and highlighting, a well-maintained Paredit -- as @pez said above. So I would recommend installing Calva with Clover and just turning off Calva's nREPL UI via that setting. That additional stuff is definitely worth having!

Thanks for the very patient and informative answers! It is a lot to take in take try out. And also New Year's Eve 😂 🎉

I think that can get very powerful.

Nice! Can you provide an example invocation of it? Perhaps to open the SimpleBrowser to a specific URL?

I don't see any updates here https://github.com/mauricioszabo/clover -- am I looking in the wrong place @mauricio.szabo?

Figured it out! Updated my VS Code config to open the Simple Browser for ClojureDocs and JavaDocs URLs: https://github.com/seancorfield/vscode-clover-setup/blob/develop/config.cljs#L219-L259

Wonderful, sorry I was away from the keyboard. Yeah, I updated the project's README to point to the gitlab repository

@mauricio.szabo Just read your post about why you're moving from GH to GitLab. I do share your frustrations about CircleCI. I used TravisCI until it became too unreliable and switched to CircleCI but I was never very happy with their setup. I added GH Actions to all my projects but initially kept CircleCI in place as well because their matrix testing was better and their caching story was better -- but GH Actions has overtaken them and I recently dropped CircleCI from all my projects and beefed up my GH Actions CI to do matrix testing and caching. GitLab is always going to be an also-ran / at-best-second in this space -- even if MS hadn't bought GH. I used to be very anti-MS but I've actually been very impressed with their increasing support for OSS across the board and I think the integrations between GH and VS Code are "best of breed" at this point. I think Copilot is "interesting" but neither very compelling nor something to get terribly upset about. I certainly have no plans to move my projects to inferior services over dogma... 🙂

I find it a bit ironic that your GH version of Clover doesn't actually have a license as far as I can see -- and your GitLab version does (but does not state what the license is in the README -- I think it's MIT?)

Yeah, it's MIT. I actually forgot to add a license, and now I'm only updating the gitlab repo

As for circleci, I do like it a lot :). I did not have good experiences with GitHub Actions, so I would not use it even if I decide to keep using GH. As for Microsoft, they indeed increased support for OSS but I still see some of the same patterns and questionable practices (to day the least) with their software. I'm not really a "free software activist", at least not anymore, but I can't really agree on how they are doing things at their side. In fact, none of my projects at GitHub have a "copyleft license" so in theory copilot would not be an issue for me. But not having a way to opt out, the transcribing of verbatim code, and Microsoft increasing incorrect and misleading info about the product =to the point of multiple Microsoft posts disagreeing with each other) doesn't sound like something I would agree.

My experience with gitlab, so far, was not really bad. It's just slower, and uglier. Things would be different if I had to migrate to bitbucket, for example 🤣

These kinds of bugs are really, really hard to debug. I remember once at Chlorine that on Atom, on a specific Mac version, if you never installed Chlorine before, the package refused to activate. No errors at console, no debug info, nothing - and only at release, minified, builds...

I'll keep an eye out and see if there's any sort of pattern to it happening. I don't use my laptop enough to see whether it happens there too (Windows/WSL2).