Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
aappleby
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
151.
▲
by
aappleby
2y ago
Is this really a new thing? It feels like they've just crammed a sliver of the same bog-standard parsing we've been doing for decades back into the CFG. I guess that's good for preventing off-by-one-based parsing errors, but
152.
▲
by
aappleby
2y ago
I already have a N100 mini-pc to play with, but now I want one of these guys too. So cute.
153.
▲
by
aappleby
2y ago
"Male and female brains are so similar that it takes a dedicated AI to distinguish between the two."
154.
▲
by
aappleby
2y ago
Minisforum BD790i with 96 gigs of LPDDR5 RAM running Ollama. I run Qwen 110b on the CPU and get around a token per second, which is enough for me to dash off a question and get an answer a few minutes later. Smaller models like CodeLlama th
155.
▲
by
aappleby
2y ago
My workstation runs a local LLM that allows me to ask deeply technical questions in plain English and receive useful, usually highly accurate (95%+ of the time) responses in a few seconds. It has no memory and requires no Internet access, s
156.
▲
by
aappleby
2y ago
Ooooo.....
157.
▲
by
aappleby
2y ago
Google Maps does stroke expansion in WebGL 1 vertex/pixel shaders. The vertex shader converts a linear path-segment "instance" into a quad with correctly beveled/extended endpoints, the pixel shader does some normalizati
158.
▲
by
aappleby
2y ago
What did you expect?
159.
▲
by
aappleby
2y ago
Hi, MurmurHash and SMHasher author here. With the code-golfing obfuscation unwound, Th64 is structured very similarly to MurmurHash. The source data is pre-mixed via "rol(x * r + i, 31)", the hash is mixed via "hash = rol(has
160.
▲
by
aappleby
2y ago
Some of it I was able to verify immediately, some I confirmed by poking around in Github repos once I knew the magic words, some I haven't verified yet. For example, I wasn't sure if there was good support for USB devices in Rust.
161.
▲
by
aappleby
2y ago
I don't need an AI to write code for me, but it is _astoundingly_ helpful to have it summarize various design options and new technology stacks without me having to scavenge Google for the obscure corner-cases I care about. I have an i
162.
▲
by
aappleby
2y ago
Google Maps extends atlases vertically in the rare case that they overflow by creating a new taller texture and blitting the old one into it. Since it's device local it takes almost no time.
163.
▲
by
aappleby
2y ago
Texture atlases will still be a thing when you're dealing with thousands or tens of thousands of glyphs in a glyph cache (some languages end up with a combinatorial explosion of glyphs due to accent marks and stuff).
164.
▲
by
aappleby
2y ago
Oh, and we had similar visualizers for atlas usage but they were live views in a popup window rendered via canvas.
165.
▲
by
aappleby
2y ago
Just wanted to let you know that you converged on the same solution (nested 1d allocators) that I came up with for Google Maps back in 2013ish. We also made heavy use of allocation bitmaps and a few other tricks to ensure that the texture a
166.
▲
by
aappleby
2y ago
I have one, it's a cute toy but I wish I'd shelled out a few bucks more for the Duo S - better form factor, 8x the ram.
167.
▲
by
aappleby
2y ago
Oh, nowhere near as bad as PS2. All the cores have sane assembly languages and they're all on the same bus.
168.
▲
by
aappleby
2y ago
"CPU modifications are minimal, involving the integration of the PPU interface into the instruction set" This absolutely reeks of bullshit and vaporware. Anyone know what this thing actually does?
169.
▲
by
aappleby
2y ago
I wrote a CH32V003 programmer that runs on a RPi Pico - https://github.com/aappleby/picorvd
170.
▲
by
aappleby
2y ago
The original SpinRite was a lifesaver back in the days of 100 meg magnetic disks, I paid for a copy and used it to resurrect both my own and my friends' hard drives a few times. It was indeed able to (usually) recover bad sectors that
171.
▲
by
aappleby
2y ago
If you click "Let's take a peek", you can never get back to the front page. That's kinda annoying.
172.
▲
by
aappleby
2y ago
Was gamedev between 1980 and 2000ish, can confirm. PS1 had no floating point unit.
173.
▲
by
aappleby
2y ago
I think the Bitboys chip was something different, the game studio I was at at the time did get actual test hardware for the Pyramid3D.
174.
▲
by
aappleby
2y ago
I remember this chip - flaky drivers but the dev board we got did work. We ended up just using Voodoo something or other, and then the first GeForce boards came out a year or two later.
175.
▲
by
aappleby
2y ago
This might interest you - https://github.com/aappleby/wideboard
176.
▲
by
aappleby
2y ago
Hi, I'm the MurmurHash guy. Neat stuff, and I'm amused that multiply-shift-xor has held up so well for all this time.
177.
▲
by
aappleby
2y ago
Bit outdated now. The CH32v003 is 10 cents, roughly equivalent to an ATTiny, and easily available.
178.
▲
by
aappleby
2y ago
The 2d to 3d transition is particularly nice
179.
▲
by
aappleby
2y ago
What's the cheapest hardware setup that can run a 70B model at tolerably interactive rates? (say 10 characters a second)
180.
▲
by
aappleby
2y ago
I was there 12 years, left a year ago. Sounds like it kept going in the same trajectory as when I left.
More ›