This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-04-29
Channels
- # asami (1)
- # babashka (20)
- # beginners (3)
- # biff (1)
- # calva (5)
- # clj-kondo (68)
- # clojure (6)
- # clojure-europe (70)
- # clojure-losangeles (4)
- # clojurescript (1)
- # cursive (6)
- # exercism (1)
- # fulcro (3)
- # hyperfiddle (23)
- # introduce-yourself (1)
- # kaocha (1)
- # lambdaisland (8)
- # lsp (6)
- # off-topic (24)
- # pathom (24)
- # specter (1)
- # tools-deps (4)
- # xtdb (4)
Quick update here on the "I'll be spending a lot of time on Biff now" thing: right after the latest release + doc updates, I thought "hey why don't I completely rewrite Yakread's entire frontend", so that is currently underway. The Biff stuff will resume as soon as that's complete, realistically in two weeks I would estimate. (I think it might be done in one, so padding to two--though of course https://en.wikipedia.org/wiki/Hofstadter%27s_law may apply here.) Since several people have expressed interest in an Electric integration, that'll probably be the next Biff thing I do. After that I'd like to at least make some documentation that addresses using Biff in a team context (e.g. using containers + CI/CD, instead of the out-of-the-box production story which is designed for solo developers), and maybe write some supporting code as needed. As for the previously discussed 1-click digitalocean deployment thing--I'm actually thinking it might be better to just make a how-to video for deploying the current regular way, as it really isn't much work beyond what the 1-click deployment would be. (There is also the https://biffweb.com/docs/tutorial/deploy/ already which has screenshots). I also https://tfos.co/p/what-if-i-started-a-nonprofit/ in which I muse about potentially open-sourcing Yakread, in which case that would become the "flagship" biff app--FYI for anyone who might be interested in hacking on that.