Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jacobobryant
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
Show HN: Biff 2.0 (Clojure web framework)
(biffweb.com)
28 points
by
jacobobryant
6d ago
|
0 comments
2.
▲
Biff.datastar: lightweight web UIs with Clojure and Datastar
(github.com)
2 points
by
jacobobryant
1mo ago
|
0 comments
3.
▲
by
jacobobryant
2mo ago
as of now neovim works great with clojure, not sure about other lisps. vs code also.
4.
▲
by
jacobobryant
2mo ago
yep, so if it's important for the application you're working on that you always run the minimum number of database queries possible, biff.graph isn't a good fit. Pathom's query planner might work as you've described
5.
▲
by
jacobobryant
2mo ago
You could always introduce an explicit caching context by doing something like `(binding [ cache (atom {})] ...)` whenever you start using some functions like this. If you were trying to use this approach inside a library then you could wr
6.
▲
by
jacobobryant
2mo ago
ah got it. yeah, in that case you can write a biff -> pathom resolver shim that works for everything. Again though the main thing is just the fact that they have two completely different query engines and aren't guaranteed to give t
7.
▲
by
jacobobryant
2mo ago
> If it weren't for those, would Pathom be a drop-in replacement? Or is there different logic? I could've written biff.graph to work with actual Pathom resolvers. In fact it wouldn't be hard to write a shim that takes Path
8.
▲
by
jacobobryant
2mo ago
> From what I hear, the main draw is separating what you want from how you get it, so your calling code can just focus on what it needs. But you can use regular functions to do that. What libraries like Pathom do is leave it open to the
9.
▲
by
jacobobryant
2mo ago
Thanks for mentioning datajet, I'll be taking a look at that for sure...
10.
▲
by
jacobobryant
2mo ago
> It's very cool you managed to make a mini Pathom - esp in so few lines of code :)) Thanks! The possibility of doing this had been on my mind for a while... and then I finally got around to trying it since all I had to do to get st
11.
▲
by
jacobobryant
2mo ago
Yeah, it's a big eye-opener. I'd like to see if I can figure out an ergonomic way to do it in Python since I do a fair amount of work in that, and passing ORM objects around isn't great.
12.
▲
Biff.graph: structure your Clojure codebase as a queryable graph
(github.com)
147 points
by
jacobobryant
2mo ago
|
32 comments
13.
▲
Biff.fx: lightweight effects system for Clojure
(biffweb.com)
31 points
by
jacobobryant
3mo ago
|
0 comments
14.
▲
by
jacobobryant
3mo ago
hehe yes. There are plenty of other languages with dominant frameworks etc; I like being in a community of experimenters.
15.
▲
by
jacobobryant
3mo ago
If everyone wants to move to biff.core that's fine with me!
16.
▲
by
jacobobryant
3mo ago
AI has been working out well for me writing Clojure, both in personal projects and at work. Documentation, not so much... I write all that by hand. For Biff I've been using AI to generate a rough draft of all the code and then I take a
17.
▲
Biff.core: system composition for Clojure web apps
(biffweb.com)
138 points
by
jacobobryant
3mo ago
|
33 comments
18.
▲
by
jacobobryant
4mo ago
As the author of a different project also named Biff, I do have to warn you that half the comments on your HN posts will be people quoting back to the future--though I haven't decided yet if that's annoying or an engagement hack!
19.
▲
Biff 2.0 sneak peak: Clojure web framework
(biffweb.com)
3 points
by
jacobobryant
5mo ago
|
0 comments
20.
▲
Isolating AI Coding Agents on Bare Metal
(blog.singlr.ai)
3 points
by
jacobobryant
5mo ago
|
0 comments
21.
▲
by
jacobobryant
8mo ago
In some informal benchmarks I wrote using queries + data from a web app I develop, sqlite queries were about 5x faster than postgres.
22.
▲
Relaunching Yakread: an algorithmic reading app
(biffweb.com)
4 points
by
jacobobryant
1y ago
|
0 comments
23.
▲
by
jacobobryant
1y ago
Thanks for the feedback. I've structured Yakread (and its predecessors) as a daily email newsletter because it increases user retention tremendously. It's much less work for users if Yakread can show up in a place they already che
24.
▲
by
jacobobryant
1y ago
I've been working on this kind of thing over the past several years (for a while full time as an attempted entrepreneur, now on the side for the past couple years). The latest iteration is https://yakread.com -- hit "t
25.
▲
by
jacobobryant
1y ago
You can do that, it's just slow if there are a lot of results. Agreed you want to keep data in your main database normalized since it's easier to reason about and avoid bugs/inconsistencies in the data. The inherent trade-off
26.
▲
by
jacobobryant
1y ago
Thanks! It's all from scratch.
27.
▲
by
jacobobryant
1y ago
yes, that's part of it.
28.
▲
by
jacobobryant
1y ago
Agreed, thanks for sharing that post. Good read.
29.
▲
Writing your Clojure tests in EDN files
(biffweb.com)
67 points
by
jacobobryant
1y ago
|
4 comments
30.
▲
by
jacobobryant
1y ago
Glad to hear it!
More ›