Clojurians Log v2

@hindol.adhya @saikyun @wilkerlucio Hey everyone, quick update since things have been fairly quiet on the Ghostwheel front for the last few months. I was a little sidetracked – or rather completely off the radar – due to another project I've been trying to get off the ground for a while and the almost-finished next release of Ghostwheel has been sitting there until recently, waiting to be finally pushed across the finish line and resolve a number of, at this point, long-standing issues. While activity on the project is likely to continue in bursts rather than continuously, I cautiously expect both the intervals between releases as well as my response time to issues and the occasional question on the Clojurians slack to become shorter. I'll be replying to open issues and Slack messages over the coming few days, if you posted here without a response or otherwise tried to get in touch with me unsuccessfully and I don't get back to you until the end of the week, feel free to give it another go if you're still interested in the project. TL;DR – Ghostwheel's alive and kicking, it just likes to take a longer nap every now and then.

This looks nice, I'll have a closer look over the next weeks to see if it makes sense for the issues addressed by it to be solved in Ghostwheel – and if so, talk to @tony.kay about merging the projects back together – or if it's better for them to continue separately.

@clojurians.net glad to hear it! 🙂 happy to hear you're okay as well

one issue I've noticed but had a hard time reproducing in a smaller project, is that in a cljs project, I've had instrumentation break a lot. is this something you've noticed?