> It would be nice if Biff weren't dependent on various ad-hoc scripts (some in bash, others in babashka), since it means newcomers to Biff (and especially newcomers to Clojure in general) have to install a variety of tools without clear purpose.
I don't find this accurate. Biff is not dependent on any bash scripts at all. There is one(1) bash script, server-setup.sh, which you can run to configure a server. It's a 112loc script which installs dependencies, configures nginx, sets up a systemd service and git deploys. I don't call this a dependency since it's literally the exact same thing as running these commands by yourself. Once you've ran it, neither your server or development env depends on it in any way. It's just a handy way to set up a server.
As for the bb scripts, yes you need to install babashka to run them. I don't see how this is different from having to install lein to run luminus apps? clojure-cli is the defacto standard tool these days after all.. babashka's deps are declarativively defined in bb.edn, i don't find it accurate to describe as "moving pieces" .
> like existing Clojure "frameworks", it still fails to feel like a Rails / Django / Laravel and feels more like "here is a project template with a bunch of decisions baked in for you".
> As I and other have already said, it depends on the specific language. Some languages scope local variables at the function level (irrespective of {} or Begin End), and other languages scope local variables inside the containing {} or Begin and End block.
And some languages do either, depending on the keyword used to declare a variable. Looking at you JavaScript(var vs let).
I understand telling people to "just google it" or "read the fine manual" on support forums where the same repetitive questions are asked a million times, but on hacker news? Why? What is wrong with asking a question that is of interest to the average reader of this thread? What's wrong with conversation?
While it's correct that each Git commit is a snapshot of the worktree, and not a diff, Git uses copy-on-write / structural sharing, which means that generally speaking adding a commit to your repository is a very cheap operation storage wise.