This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-25
Channels
- # announcements (21)
- # babashka (7)
- # beginners (27)
- # calva (7)
- # chlorine-clover (3)
- # cider (1)
- # clerk (21)
- # clojure (24)
- # clojure-europe (28)
- # clojure-finland (3)
- # clojure-nl (1)
- # clojure-norway (5)
- # clojure-uk (2)
- # clojurescript (13)
- # clr (2)
- # conjure (1)
- # consulting (1)
- # datahike (1)
- # datomic (13)
- # fulcro (3)
- # graalvm (33)
- # gratitude (7)
- # honeysql (7)
- # humbleui (12)
- # hyperfiddle (26)
- # interop (11)
- # introduce-yourself (4)
- # jobs-discuss (8)
- # lsp (26)
- # malli (6)
- # nbb (11)
- # polylith (26)
- # practicalli (1)
- # rdf (3)
- # re-frame (7)
- # reitit (10)
- # releases (2)
- # shadow-cljs (1)
- # tools-deps (15)
Hi folks - so, an update on the future of these projects: I am planning some really big changes on Chlorine (and maybe on Clover too - we'll see). Pulsar (our Atom fork) is quite stable, and currently is also running tree-sitter for Clojure (which is a big win too) so I am, right now, thinking on how I could leverage all of this to handle future interesting ideas. Currently, Chlorine (and Clover) support different kinds of REPL: a "Pure Socket REPL", a "Socket REPL enhanced by UNREPL", nREPL, and the Shadow Remote API. As you can probably imagine... it's too much. So, future versions of Chlorine will drop support for Socket REPL. It is simply not worth it, and it's a big source of bugs. I'll focus basically on nREPL alone, and Shadow Remote. On the Clojure landscape, there are a HUGE number of plug-ins that do a wonderful job on connecting to nREPL, so what I will focus is data visualization - meaning, I'll try to piggie-back on other projects from the #C0BQDEJ8M and #C02V9TL2G3V, like Kindly (https://scicloj.github.io/kindly/) and Portal, to get visualizations inside the editor. Currently, Chlorine already kinda supports this but I want to make a better suport for it too.
Future things I want to do: get a better integration with #C03KZ3XT0CF debugger, like showing typing information that FlowStorm returns inside the editor, and maybe add some tracing inside the editor - we'll see
Also, considering that I now control both the editor and the plug-in, I am thinking about adding some UI stuff that may help Chlorine - an example could be a way to have "scratch" editors that we can test things (and that will be discarded later), and integrate with Tree-Sitter for a faster parsing library for Chlorine. Also, I want to make Pulsar a better editor for ClojureScript, so I am making an equivalent of Joyride for it, and a package generator that creates a package with ClojureScript instead. Finally, one of the things I am quite excited to try, but might take a while: I want Pulsar to be able to create "stand alone" editor components - basically, to open "auxiliary editors" that can be pointed to functions, blocks, etc - and that keep in sync with other editors. One idea for that is to allow to edit a single function without needing to open the file, scroll to the function, etc. I'm still not sure if this will be easy, or really hard but again - we bumped 15 Electron versions already, so... it might just work :rolling_on_the_floor_laughing:
