Edit: moved draft to Philosophy of Biff . Will publish soon.
1 Like
Just finished the above draft and changed the title to “Philosophy of Biff.” For comparison to other frameworks and approaches/“should you use Biff”, I think I’ll just add a short section to the introduction .
Made a few small edits, and added this at the end:
jacobobryant:
There is a bit of a contradiction here: Biff is designed so it can be adapted to your needs, and yet if it doesn’t meet your needs you’re supposed to use something else. The distinction is that Biff’s adaptability is meant to accommodate your project as it grows . If you think that Biff might be a good fit for a new project as long as you change X, Y and Z, you might find it’s easier to simply compose the libraries yourself without Biff. You can always read Biff’s source code for inspiration. But if Biff meets your current needs as-is, you should be able to have confidence that it’ll adapt to meet your future needs as well.
Biff is itself a principled component within the larger Clojure ecosystem.