Unrelated, but gorgeous website!
Readit Newswillcodeforfoo commented on How to think about durable execution hatchet.run/blog/durable-... · Posted by u/abelanger
For what it's worth, the landing page is one of the most beautifully designed things I have seen in a long time. Congratz on the launch, didn't want to be so negative. I just hate that this is built on top of Stripe :(
I liked it too, reminds me of zed.dev...
willcodeforfoo commented on Claude Sonnet 4.5 anthropic.com/news/claude... · Posted by u/adocomplete
I've really got to refactor my side project which I tailored to just use OpenAI API calls. I think the Anthropic APIs are a bit different so I just never put in the energy to support the changes. I think I remember reading that there are tools to simpify this kind of work, to support multiple LLM APIs? I'm sure I could do it manually but how do you all support multiple API providers that have some differences in the API design?
Unrelated, but wondering if anyone here could recommend a Darktable-ish web-based photo organization app, less focused on editing but supporting tagging, starring, etc.?
willcodeforfoo commented on Visualizing 13M Bluesky users joelgustafson.com/posts/2... · Posted by u/joelg
Love this kind of post! I was surprised to see you really can drink from the firehose:
brew install websocat
websocat wss://bsky.network/xrpc/com.atproto.sync.subscribeRepos
willcodeforfoo commented on What you can get out of a high-quality font sinja.io/blog/get-maximum... · Posted by u/OlegWock
Nothing really to add... other than the type on that page looks gorgeous.
willcodeforfoo commented on Stapler: I remade a 32 year old classic Macintosh app blog.gingerbeardman.com/2... · Posted by u/msephton
Nice! Similar to Brett Terpstra's Bunch[1] which has a GUI-less approach.
[1]: https://bunchapp.co/
willcodeforfoo commented on Show HN: Searchable Kubernetes CSI provider listing storageclass.info/storage... · Posted by u/noctarius
I guess your biggest issue may be the multiple writer problem, but you'd have the same issue on a local disk. The second multiple writer are supposed to update the same files, you'll run into issues.
Have you thought about TCP sockets between the apps and sharing state, or something like a redis database?
Hmm, maybe... although that wouldn't help with the aggregating multiple nodes issue, or would require a lot of app-side logic.
In this example, I have 200GB of ephemeral storage available on each node, ideally I'd like something like this:
node1: /tmp/data1 (200GB free space)
node2: /tmp/data2 (200GB free space)
node3: /tmp/data3 (200GB free space)
node4: /tmp/data4 (200GB free space)
node5: /tmp/data5 (200GB free space)
willcodeforfoo commented on Show HN: Searchable Kubernetes CSI provider listing storageclass.info/storage... · Posted by u/noctarius
You need some type of cluster-wide shared memory?
Yep! But I don't have access to any block devices on nodes, only the local paths so I'm not sure OpenEBS or Ceph would work...
willcodeforfoo commented on Show HN: Searchable Kubernetes CSI provider listing storageclass.info/storage... · Posted by u/noctarius
Somewhat related: can anyone recommend a simple solution to share each node’s ephemeral disk/“emptyDir” across the cluster? Speed is more important than durability, this is just for a temporary batch job cluster. It’d be ideal if I could stripe across nodes and expose one big volume to all pods (JBOD style)