Clojurians Log v2

PSA: someone (chat logs are gone, so don't remember who) asked a week or so ago if it'd be better to hold off on trying out biff until after I've finished the next release (which will be large). I'm updating my recommendation from "go ahead" to "wait" in case anyone is thinking about trying it out soon but hasn't just yet. I'm in the middle of working on the release; hopefully it'll be out next week (though the week after wouldn't surprise me). I was planning to make the upgrade backwards compatible, but after having finished most of the code I'm not sure if it would make much difference. There are a lot of structural changes (it's practically a rewrite), and either way you'd have to migrate code to take advantage of the new structure. Easiest way to migrate an existing project would probably be to just start a new project (with the updated project template) and copy the application code over. If anyone actually has a current biff project, let me know as well. I know some people have tried it out a bit, but I'm operating on the assumption that most likely no one other than me is actively using biff (I'd expect more support requests if that were the case 🙂 ).

@foo Just because you don't have any support requests doesn't mean people aren't using your code. I think Paula has a whole pile of happy, silent ghost users for Asami, for example. 😉 If you don't have a Slack Archive stream in Clojurians Zulip yet, you should totally beg @eval2020 for one. See: https://clojurians.zulipchat.com/#narrow/stream/185617-crux/topic/Slack-archive.20in.20this.20stream/near/229196307 I realize many people aren't ready to switch from Slack to Zulip yet, but it's great to have a proper immutable record of what happens in the Slack channel.