pkghost

Joined 16 years ago

Karma
809
Submissions
184
Member since
Mar 23
www.cameronboehmer.com
View on Hacker News

Recent submissions

Comment · 1 month ago
"Emacs, rewritten in Rust — unleashed on the GPU, fixing what 40 years of C never could."
Comment · 2 months ago
Having gone down the worktree rabbit hole for a month or so, I am giving up in favor of multiple checkouts to enable many agents to work across many repos.

Worktrees worked great for me when my agents' work was mostly contained to a single repo (they got me to finally hitting rate limits, not that that was a goal). As my homelab scales, agents increasingly work across multiple repos, and that's where (my approach to) worktrees broke down; agents were spawned in a repo worktree and so avoided stepping on the toes of other agents in the same repo without any special instruction, but as soon as they needed to touch another repo, they would default to working in that repo directly, without a worktree, and thus collide with other agents, and muddy a merge process that expected the main repo clone to be clean (which turns out to have been an unnecessary design quirk, but resolving it would still not stop agents from stepping on each other's toes in secondary repos).

After a detour through ZFS dataset clones and some mounting magic that made /srv/src/ appear to be a distinct hierarchy for each agent process, I am simplifying even further and giving each agent a bare directory (sth like /srv/dev/<slug>/) where they can check out any repos they want. The git remote (/srv/git/) becomes the only integration point.

Maybe I should just bite the bullet and move into containers, but performant as they are the ergonomics still bum me out.

Edit: I may actually hold on to ZFS datasets with mounting magic. It does add a bit of complexity to dev tools, but it also reduces path-based trust bloat in harness configs, provides some interesting zfs features (zfs diff, etc)... And it's done.

Comment · 2 months ago
> on an admittedly overpowered laptop: 15 tokens/s in power save mode on this MacBook M5 Max 48GB, and 30 in performance mode.

Okay, so I'm here to brag a little. I love that I also get 30 t/s on $1500 of decade-old hardware: dell r720 w 2x tesla v100s!

Comment · 3 months ago
Here's the thing: life also imitates art. If you invert your load-bearing assumption, it could be that he just reads too much slop. But my honest take? You might be right.
Comment · 4 months ago
> And then there's homeopathy which is a largely unrelated and entirely nonsensical thing.

And be careful with that dismissal! Not that I'm helping my case, here, but Pollack doesn't think it's baloney (see related chapter in his book "The Fourth Phase of Water").

Comment · 4 months ago
Folks still sleeping on structured water.

While admittedly contested and only reproduced by a few labs outside Gerald Pollack's at University of Washington, there is a solid case that it could play a role in transporting water and sap to the tops of trees. At least, it's involved in the motion induced in hydrophilic tubes when there is sufficient ambient radiant energy (uv/infrared).

Relevant papers:

"Exclusion-zone water inside and outside of plant xylem vessels." 2024 Scientific Reports. https://www.nature.com/articles/s41598-024-62983-3

"Surface-induced flow: a natural microscopic engine using infrared energy as fuel." 202 Science Advances. https://www.science.org/doi/10.1126/sciadv.aba0941

"Long-range forces extending from polymer-gel surfaces." 2003 Phys. Rev. E. https://link.aps.org/doi/10.1103/PhysRevE.68.031408

Pollack's site: https://www.pollacklab.org/

Some critiques of Pollack's theory:

Schurr, J.M. (2013). Phenomena associated with gel–water interfaces: analyses and alternatives to the long-range ordered water hypothesis. J. Phys. Chem. B, 117(25), 7653–7674. https://doi.org/10.1021/jp302589y Elton, D.C., Spencer, P.D., Riches, J.D. & Williams, E.D. (2020). Exclusion zone phenomena in water — a critical review of experimental findings and theories. Int. J. Mol. Sci., 21(14), 5041. https://doi.org/10.3390/ijms21145041 (open access; the most thorough critical review) Elton, D.C. & Spencer, P.D. (2021). Pathological water science — four examples and what they have in common. In Water in Biomechanical and Related Systems (Biologically-Inspired Systems, vol. 17), pp. 155–170. Springer. https://doi.org/10.1007/978-3-030-67227-0_8 (preprint: https://arxiv.org/abs/2010.07287)

Comment · 6 months ago
Based on the list of contenders feels like you might be missing rsync.net?
Comment · 6 months ago
Comment · 6 months ago
Comment · 8 months ago
“While the attraction is clear, the underlying motivation is not,” he said.

Nobody involved in the study or the article has ever done even a small dose of psilocybin and interacted with crystals.

Comment · 1 year ago
they did not use RAG for these tests... how are we supposed to take the report seriously when it does not demonstrate even a cursory understanding of nature of LLMs?
Comment · 1 year ago
It's bananas!

If the claim these folks make is "time spent struggling through a default config on an unfamiliar machine" > "time saved by crafting an workshop to fit your mind", then we are not the same.

(Probably, the dividing line here is time spent coding vs time spent managing infra.)

Comment · 1 year ago
for the laconic and latin-leaning, NB (nota bene) means "note well"
Comment · 1 year ago
for the laconic and latin-familiar, NB stands for nota bene, or "note well".

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton