Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
wgjordan
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
wgjordan
4d ago
It's using a couple textbook [1] LLM tropes, 'negative parallelism' with a 'here's the kicker' tone. [1] https://gist.github.com/ossa-ma/f3baa9d25154c33095e22272c631...
2.
▲
Slicing Chrome's Zucchini patches in half
(willjordan.us)
1 points
by
wgjordan
14d ago
|
0 comments
3.
▲
Show HN: go-binsync – Go binary patches up to 67× smaller than bsdiff
(github.com)
5 points
by
wgjordan
20d ago
|
0 comments
4.
▲
by
wgjordan
23d ago
ad hominem.
5.
▲
by
wgjordan
2mo ago
The idea is for you to be able to publish a stateful app 'everywhere' that moves with your workload without micro-managing regions or resources, like a traditional CDN does for static content. The built-in replicated SQLite is wha
6.
▲
by
wgjordan
2mo ago
Pretty much! It's not dynamic memory hotplug or resizing, just dynamic billing. Usage is based on the actual RSS used by the app so you can think of the VM's defined size as just a limit, for both CPU and RAM. This means you don&#
7.
▲
by
wgjordan
2mo ago
Thanks! Yes, the write-replication part is syzy, which hooks into the standard unmodified sqlite engine that reads and writes normal sqlite db files locally - syzy just keeps multiple instances in sync by capturing writes and applying them
8.
▲
by
wgjordan
2mo ago
These are both later-stage detail questions for when this project is further hardened for production workloads, but here's where each of these currently stands: - Yes, there is a post-restore kernel reseed hook that happens after fork,
9.
▲
by
wgjordan
2mo ago
Thanks for the kind words! > I didn't immediately spot the durability contract for volumes -- local NVMe like Fly, or sitting on some underlying system like EBS? Persistent volumes use local NVMe that continuously syncs to object st
10.
▲
by
wgjordan
2mo ago
Thanks! I tried to make the sandbox-eval stdin interface as simple as possible so you could easily plug it anywhere. The executable docs run an actual full shell in a VM, since they're so fast and cheap to spin up- I hope the example m
11.
▲
by
wgjordan
2mo ago
> although why would you use it for evil I couldn't help it! Ben Johnson recently wrote a Litestream post touching on this topic [1]: > multiple-writer distributed SQLite databases are the Lament Configuration and we are not expl
12.
▲
Show HN: Kedge – Full-stack cloud with forkable VM snapshots and global SQLite
(kedge.dev)
141 points
by
wgjordan
2mo ago
|
25 comments
13.
▲
by
wgjordan
2mo ago
> As such, if you pirated a book and had to pay $3000 for that one instance, I don't think you'd like it if I said you should have paid $30K or $300K instead. If you pirated a book for personal use the amount of liability would
14.
▲
by
wgjordan
2mo ago
Your 'with 1m context window' implied that some manually-curated task 'chunks' would overflow smaller context windows (eg 200-400k tokens). If you're instead curating chunks small enough to avoid getting burned on l
15.
▲
by
wgjordan
2mo ago
> With 1m context window there is no reason for a single task to require compaction Only if money is no object. Cache reads are cheap (10% of uncached input costs) but definitely not free, and cached reads dominate session costs at long
16.
▲
by
wgjordan
4mo ago
Looks like a more detailed followup statement was just posted today: https://bricksandminifigs.com/blog/blog/2026/05/28/bricks-mi...
17.
▲
by
wgjordan
4mo ago
That's a perfectly cromulent meaning of the word.
18.
▲
by
wgjordan
4mo ago
https://en.wikipedia.org/wiki/Aladdin The argument, as I understand it is that the "theft" is in quotes because it's not literally copyright infringement, but fair use of an old public-domain folk tale t
19.
▲
by
wgjordan
4mo ago
Don't miss related HN threads from the original authors: https://news.ycombinator.com/item?id=28861204 https://news.ycombinator.com/item?id=48086249
20.
▲
by
wgjordan
4mo ago
A real example, from Facebook's 2021 outage [1]: > Our primary and out-of-band network access was down, so we sent engineers onsite to the data centers to have them debug the issue and restart the systems. But this took time, becaus
21.
▲
by
wgjordan
5mo ago
https://blog.davidv.dev/posts/minimizing-linux-boot-times/
22.
▲
by
wgjordan
6mo ago
Thanks for the extra details, the frontrun benchmark numbers seem compelling for various cold-read use cases. A system that combines both WAL frames with cold-read-optimized grouped pages is another interesting point in the design-space. Tu
23.
▲
by
wgjordan
6mo ago
Nice set of experiments! I appreciate that you're running benchmarks on real object storage setups to validate rapid design variations. (Meta-note: I love how agents have recently made this kind of experimental-research work possible w
24.
▲
by
wgjordan
6mo ago
Anthropic uses it across all their websites, here's a typical example where the effect is obvious as you scroll down: https://claude.com/solutions/agents I could be wrong, but my simple guess is that it's bec
25.
▲
by
wgjordan
6mo ago
Sounds like a promising idea, but a blog post with bits of implementation code is not a "Show HN", there's nothing to try out here. See the guideline [1]: > Off topic: blog posts, sign-up pages, newsletters, lists, and oth
26.
▲
by
wgjordan
8mo ago
Yeah, the article showed that the high-dose intervention (modeled after von Noorden's famous century-old 'oat cure') is most effective. A large bowl of oatmeal (100g) all 3 meals for 2 days, 6 large bowls total. 6 weeks of &#
27.
▲
by
wgjordan
8mo ago
It's well known that an oatmeal diet lowers cholesterol (the article itself cites a 1907 'oat cure' in its intro). The new finding here is insight into the exact mechanism- a short-term, high-dose oatmeal diet (300g/day
28.
▲
by
wgjordan
8mo ago
> It's like a dozen paragraphs, forming one complete argument. Is this too much material to take in all at once, in this brave new TLDR tomorrow? The issue is not that you cited a dozen-paragraph argument, it's that you inlined
29.
▲
by
wgjordan
8mo ago
Also worth noting (as a sibling comment pointed out) that despite these assurances the untested legal risks of AGPL-licensed code may still cause difficulties for larger, risk-averse companies. Google notably has a blanket policy [1] bannin
30.
▲
by
wgjordan
8mo ago
This clarification is helpful, thanks! The README currently implies a slightly different take, perhaps it could be made more clear that it's suitable for use unmodified in closed source products: > The AGPL license is suitable for o
More ›