Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
vlowther
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
vlowther
5mo ago
It also isn't a unique thing. See (for example) the entire history of, well, pretty much any country. There is a reason Utopia literally means "no place". * Genocide of the natives? Literally all countries in the Americas,
2.
▲
by
vlowther
5mo ago
Pretty sure it is sexually transmissible, so I would not be too sure about that.
3.
▲
by
vlowther
5mo ago
Same. Opencode + oMLX (0.3.4) + unsloth-Qwen3-Coder-Next-mlx-8bit on my M5 Max w 128GB is the sweet spot for me locally. The prompt decode caching keeps things coherent and fast even when contexts get north of 100k tokens.
4.
▲
by
vlowther
6mo ago
The 8 bit MLX unsloth quant of qwen3-coder-next seems to be a local best on an MBB M5 Max with 128GB memory. With oMLX doing prompt caching I can run two in parallel doing different tasks pretty reasonably. I found that lower quants tend t
5.
▲
by
vlowther
6mo ago
No really, no. the last thing Github needs is yet another vibe coded fork of a mostly vibe coded app in the first place. If I ever get around to vibe rewriting-it-in-go I might share that.
6.
▲
by
vlowther
6mo ago
MBP M5 Max. 128GB ram. oMLX. unsloth-Qwen3-Coder-Next-mlx-8bit. opencode with the telemetry stripped out. This seems to be the sweet spot for now for my local dev. Helps me to not accidentally blow through $100 in Claude tokens in a day
7.
▲
by
vlowther
6mo ago
In my case, "background writes" literally means "do the io.WriteAt for this fixed-size buffer in another goroutine so that the one servicing the blob write can get on with encryption / CRC calculation / stuffing the
8.
▲
by
vlowther
6mo ago
My usecase was building an append-only blob store with mandatory encryption, but using a semaphore + direct goroutine calls to limit background write concurrency instead of a channel + dedicated writer goroutines was a net win across a wide
9.
▲
by
vlowther
7mo ago
If the performance charts are to be believed, this has uniformly worse performance in fetching and iterating over items than a boring old b-tree, which makes it a total nonstarter for most workloads I care about. It is also sort of ironic t
10.
▲
by
vlowther
7mo ago
That is the most cursed description I have seen on how defer works. Ever.
11.
▲
by
vlowther
8mo ago
Microsoft Active Career Copilot 365 ONE, thankyouverymuch.
12.
▲
by
vlowther
9mo ago
It took quite a bit of scrolling until I found my old faves of dexed and zynaddsubfx, and I didn't see Helm ( https://tytel.org/helm/ ) at all.
13.
▲
by
vlowther
9mo ago
None of the big browsers can be trusted at this point. Firefox is at best the least worst out of the big cross platform browsers.
14.
▲
by
vlowther
9mo ago
DOS, early Windows, and early MacOS worked more or less exactly that way. Somehow, we all survived.
15.
▲
by
vlowther
9mo ago
No, you cannot. Our abstract language abilities (especially the written word part) are a very thin layer on top of hundreds of millions of years of evolution in an information dense environment.
16.
▲
by
vlowther
11mo ago
Only if you are doing in-place updates. If append-only datastores are your jam, writes via mmap are Just Fine: $ go test -v === RUN TestChunkOps chunk_test.go:26: Checking basic persistence and Store expansion. chunk_te
17.
▲
by
vlowther
11mo ago
Before it was an ACID compliant database, it was also the fastest backup solution on the market: https://bofh.bjash.com/bofh/bofh1.html
18.
▲
by
vlowther
1y ago
It isn't even really that -- most CLI tools are single-threaded and have a short lifespan, so your memory allocation strategy can be as simple as allocating what you need as you go along and then letting program termination clean it up
19.
▲
by
vlowther
1y ago
"I came up with a step-by-step plan to achieve World Peace, and now I am on a government watchlist!"
20.
▲
by
vlowther
1y ago
That sort of thing is why I wrote my own DHCPv4 server that is directly integrated with the core product at $DAYJOB. 10 years ago. Having the DHCP server determine how to handle PXE requests straight from the machine database made my life
21.
▲
by
vlowther
1y ago
Just need to make sure all your computation is done in a volume with infinite surface area and zero volume. Encoding problem solved. Now then, how hyperbolic can we make the geometry of spacetime before things get too weird?
22.
▲
by
vlowther
1y ago
I still miss my Trackman Marble FX. Never found a trackball design as elegant and useable as it was. https://www.lenzg.net/uploads/images/Trackman_Marble_FX.jpg
23.
▲
by
vlowther
1y ago
From I Palindrome I, few albums later on Apollo 18: Son, I am able, she said, though you scare me. Watch, said I. Beloved, I said, watch me scare you though. Said she, able am I, son. Brilliant.
24.
▲
by
vlowther
2y ago
Give monthly donations to your local NPR affiliate. Most of them have decently middle-of-the-road biased news, and a few have really good music programming (looking at you, KUTX).
25.
▲
by
vlowther
2y ago
CoW adaptive radix trees are the entire basis of $WORK's in-memory database -- we use them to store everything, then use boring old btrees to handle sorting data in arbitrary ways. A nice, performant persistent CoW radix tree would be
26.
▲
by
vlowther
2y ago
$WORK project heavily utilizes the test op to enable atomic updates to objects across multiple competing clients. It winds up working really well for that purpose.
27.
▲
by
vlowther
2y ago
I reach for adaptive radix trees over b-trees when I have keys and don't need to have arbitrary sort orderings these days. They are just that much more CPU and memory efficient.
28.
▲
by
vlowther
2y ago
What is the hassle with maintaining hydraulic disk brakes on a bicycle? On my motorcycle, you replace the brake fluid and inspect the rotors to make sure they are in tolerance every couple of years, check the pads for wear, the lines for d
29.
▲
by
vlowther
2y ago
Can't share my references with you directly, the implementation I wrote is closed-source and is heavily intermingled with other internal bits. But I can provide examples: 1. syscall.Iovec is a struct that the writev() systemcall uses
30.
▲
by
vlowther
2y ago
Having written one of these, a few optimizations will go a long way: 1. syscall.Iovec allows you to build up multiple batches semi independently and then write them all in a single syscall and sync the file with the next one. It is a good b
More ›