Fork me on GitHub
#biff
<
2022-10-13
>
Jacob O'Bryant00:10:16

Whilst upgrading Yakread to the new Biff version, I got sucked into making another release: https://github.com/jacobobryant/biff/releases/tag/v0.5.3

Jacob O'Bryant00:10:12

Summary is that Biff is great at handling uniqueness constraints now!

clojure-spin 1
Jacob O'Bryant02:10:05

Platypub's date picker has a new look--thanks @trost.mario! (https://github.com/jacobobryant/platypub/pull/86)

🙏 1
🙌 1
David Mays10:10:21

New to Slack so let me know if questions go in a different place. I'm interested in learning Biff. It seems like when creating a new Biff project, it's looking in the wrong place for my commands (probably since I'm currently on Windows.) • Says 'clj" command not found, but I have v1.11.1 • 'bb' command not found, but I have v0.10.163 REPL • Says needs a higher version of Java, have 17 • Says need 'rlwrap', this I do not have. Do I need to tell Biff to look for commands somewhere besides the default on Windows?

Jacob O'Bryant16:10:52

Hi! This is the right place. This is probably something I need to fix. I'll respond in more depth in a bit, after the meetup that's starting in 5 minutes 🙂 .

macrobartfast17:10:28

Welcome aboard! As Jacob said, this is the right place to ask those questions. I’m on the learning path and I’ve had great help here.

🙌 1
Jacob O'Bryant19:10:31

First question--how are you running the new project command? are you using WSL? (I use WSL myself--I'm not aware if running bash scripts on windows is even possible or not)

Jacob O'Bryant19:10:23

I've assumed a unix environment, hence the new project script being a bash script. I guess I should mention that on the getting started page. However I did convert most of the tooling this week from bash to babashka, so it might not take me much time to get it working on windows without WSL if that'd be helpful.

David Mays06:10:13

Hope the meetup went well! Definitely don't go rewrite anything for one lone Windows guy, it's actually a good excuse to get back on Linux haha. Babashka seems pretty cool and a good direction, and that it will probably be easier to get things working on Windows. I haven't used WSL, but it does seem bash scripts work on Windows. Might just be after having installed Git which comes with Git Bash, but your script did run for me! I'm still super new to everything, but it seems like an awesome project.

David Mays13:10:03

Also I need to give WSL a try too.

Jacob O'Bryant22:10:31

Sounds good! I'll try fiddling with git bash for at least a few minutes sometime; if it's easy to support windows without wsl then might as well. In the mean time I can definitely recommend WSL! I've been using it for I think almost 2 years now? I was on arch linux for 10 years and then decided to at least try out windows again for a bit when I got a new laptop. I was pleasantly surprised with it and decided to keep it! But I still don't trust MS to not screw it up so I'm sticking on Windows 10 until I get forced to upgrade

David Mays04:10:42

There are some weird things on full windows, like clj / other command line tools needing some things double quoted.

David Mays10:10:11

I originally hadn't used WSL thinking it would be "more complicated" but actually getting Clojure running on plain Windows was a bit tricky. Almost no tutorials mentioned a Windows install. Especially the clj command line tools didn't ever seem to install for me. I finally got things working with this guy's step by step install using Scoop, a command line installer for Windows: https://github.com/littleli/scoop-clojure

David Mays11:10:37

Also this project uses Babashka for the back end as well, and was designed for Clojure newbies like me on Windows: https://github.com/kloimhardt/bb-web

David Mays11:10:31

But ya not talking you into using Windows, I'm the one that needs to try WSL anyway haha. Thanks I'm excited to try Biff!

David Mays14:10:46

Sorry for the flood of messages. Tried Biff install on a WSL2 Ubuntu instance, and actually get the same problem: it doesnt seem to find things like clj? The last line shows clj command working:

macrobartfast14:10:36

keep them coming until you’re up and running.

Jacob O'Bryant15:10:57

oh, actually it looks like what's happening is you're not running the setup script, you're just downloading it and printing it to the console. you're seeing those error messages just because they're part of the script, not because the commands haven't been found

Jacob O'Bryant15:10:17

need to run bash <(curl -s ) instead of just curl . you could try that again under plain windows too

David Mays03:10:34

Thank you!! I'm dumb, that totally worked, yay. And thanks for pointing me towards WSL, it's pretty amazing you can have the VS Code side open in windows, and just type "code ." in the WSL folder and it's all connected. Didn't actually get it going in Windows, but I I'll like this even better. Thanks so much for your patience! I'm really excited about Biff. Also a bit curious if you've ever tried Hotwire, and how it compares to HTMX? Thanks again.

Jacob O'Bryant04:10:29

excellent! glad it's working :). (I'm still planning to give git bash a whirl though just for fun at some point!) I haven't used hot wire, but from what I read, I think htmx is a bit more low level? so hotwire might take less work for common use cases, but there could be situations where it ends up getting in the way where htmx wouldn't (?). that was my impression at least! I know the htmx author has talked about htmx vs hotwire before; that might be worth looking up.

Jacob O'Bryant04:10:47

https://discuss.hotwired.dev/t/hotwire-vs-htmx-comparison/1614 this has a comment from the htmx author, and someone from Basecamp it looks like (?)