Wow. I'm the creator of Calva and I can tell you that I do not have an opinion on how to use it. I would never say something like that, and now I wonder what I could have said that was interpreted this way...
By default Calva Paredit overrides three or so keyboard shortcuts. This is to help the users to not accidentally delete brackets, which in turn keeps the support questions down about broken Clojure code. I have tried to make it super easy to disable these overrides. There's a command for it. There's a button in the toolbar for it, and there's a setting for it.
There's also a setting for removing all Paredit bindings, even those that are not overriding any default ones. (This setting is for people who use Paredit, but want to provide their own shortcuts entirely.)
As a Clojure editor tool smith it pains me that this is the case. Especially for ClojureScript where I spend most of my time. I really want to fix this.
For JVM interop, I think Cursive (IntelliJ Clojure plugin) is smart enough to help with autocompleting Java libraries.
Thanks! Even though I am not super familiar with Ports & Adapters, this article made Polylith click in a way that no other article or video I've so far encountered has succeeded with. Composable mini-cores. Brilliant!
I am a member of the Interactive Programming cult, being dogmatic around one thing in particular: I demand that programming is joyful, else it is not for me.
Clojure changed my life. It made me realize how fun it is to code and switch back to being a programmer. This makes me a much happier person and thus a better husband and father. Never looking back. The Clojure Way just fits me perfectly.
I made a video about some of the benefits of using ClojureScript for developing VS Code Extensions. It's a short (9 minutes) demo of me hacking on an extension of mine, trying to relay what it is we Clojure peeps mean when we speak of Interactive Programming (aka REPL Driven Development). I find it super powerful when hacking on extensions, since restarting the Dev Extension Host can be pretty disruptive. And having to halt the program in the debugger to inspect it often does does not fit when searching for the cause of a problem.
It is definitely true that Joyride can't make VS Code as fully extensible as Emacs is. VS Code is not designed this way. And also some extensibility from an extension need to come from an extension manifest when an extension loads, so Joyride can't declare new commands for instance. I'm guessing that is the simplest thing in Emacs.
Having, draw a rendom number out of a hat, 50% of Emacs extensibility at your REPL is fantastic, and worth pursuing. Joyride can do everything a VS Code extension can do, except the things i mentioned above, and anyone who has used some VS Code extensions knows that that is a lot.
However, the self documenting part described above is not out of reach. Most of the code building up the VS Code API is open source. Same goes for many of the extensions. Looking up and navigating to any of that code is possible. Perhaps a lot of work would need to be put in, but it is possible.
And when/if VS Code decides to allow new commands without the manifest (maybe with a confirmation popup), Joyride is super well positioned as a way to customize your VS Code (well, from users that don't hate parens).
As the co-creator here I'd like to add that Joyride is taking the very first baby steps here. We hope a lot of people want to try it and provide feedback to inform our next steps.
NB: The video has a target audience of people who know Clojure and its strengths. Especially how the REPL is used. I hope HN will see beyond the parens. =) It should make some sense anyway. Especially if you have some Emacs scripting experience, because that is where most of the inspiration to Joyride comes from.
Tbh, the last nights have been less about sleep and more about hacking on Joyride. =)
But usually I do get sleep. The question we should ask is if borkdude sleeps? He's doing about 100X as much as I do. Maybe there are hundreds of borkdudes.
Fantastic work on the extension. In terms of ideas for next steps, my suggestion would be to consider automating the process of creating and invoking cljs files. One big use I can see for this is creating ad hoc scripts to do stuff in the editor. If you could pop up an editor via some shortcut that would allow you to create a script and bind it to a shortcut, that would make using Joyride really seamless.
By default Calva Paredit overrides three or so keyboard shortcuts. This is to help the users to not accidentally delete brackets, which in turn keeps the support questions down about broken Clojure code. I have tried to make it super easy to disable these overrides. There's a command for it. There's a button in the toolbar for it, and there's a setting for it.
There's also a setting for removing all Paredit bindings, even those that are not overriding any default ones. (This setting is for people who use Paredit, but want to provide their own shortcuts entirely.)