Open Collective
Open Collective
Loading
Future of Chlorine
Published on July 3, 2023 by Maurício Eduardo Chicupo Szabo

Hi folks!

After the Atom sunset, I've been working a lot in the Pulsar Editor - it's a fork of Atom, and that will be the new target for Chlorine.

So, now that things are becoming more stable, I want to write a little bit about future upgrades:

1. Use tree-sitter to parse the source. This will make Chlorine faster to evaluate code, specially on big files
2. Better support for nRepl. Unfortunately, the idea to use Socket REPL didn't work well. After a long time, I still see bugs and weird artifacts in some runtimes, so I'll drop support for it and invest time on nRepl instead. This will make everything better, I promise!
3. Better support for ClojureScript. There are some weird bugs that I want to fix, and they are on the way to be completely fixed so that we'll have a better ClojureScript experience too with shadow-cljs
4. Faster. Bumping some dependencies will make things better and faster. Also, Pulsar is bumping some node versions, which means more speed both on the plug-in side, and also on the renderer side
5. Leverage community tools. I'm studying a way to integrate Portal, some visual tools from the data-science group, into Chlorine, meaning we'll be able to plot, draw, and inspect elements way better than we do now
6. Integration with FlowStorm. For people that are not aware, FlowStorm is a trace debugger. Integrating it into Chlorine will give a better experience than the old "watch expressions" from LightTable

That's it for now, I'll try to be more active in this channel too!