aappleby

26 ms·

361.
by aappleby 4y ago
Pattern matching and comparing to a reference implementation. Think of it like a giant Sudoku crossed with a maze.
362.
by aappleby 4y ago
Yay, the only bit of the die I couldn't transcribe for GateBoy! Looking forward to integrating this into the big simulator mess. Three frames per second here we come:D.
363.
by aappleby 4y ago
Hey guys, found the antivaxxer.
364.
by aappleby 4y ago
Off-grid domestic water uses tanks fitted with rubber bladders that keep the water at a roughly constant pressure and reduce the frequency the pump has to cycle.
365.
by aappleby 4y ago
My note-taking system, basically the same since college: 1. Write down every nontrivial observation in a flat text file. 2. When that file gets longer than a few pages, transcribe it into a new file while leaving out or combining or rephra
366.
by aappleby 4y ago
The overabundance of both frameworks and CPU performance causes programmers to massively overdesign systems that end up underperforming.
367.
by aappleby 4y ago
Old comment thread: https://news.ycombinator.com/item?id=32682264#32683540
368.
by aappleby 4y ago
Hey, the new branding looks exactly like what I suggested in a similar HN comment a few months ago. Good job (finally) USB people.
369.
by aappleby 4y ago
The N64's CPU was dramatically more powerful than the PS1's, but it was partly hamstrung by having to share the high-latency RDRAM bus with the GPU. The 4k "texture stamp" memory was an absurd limitation and nobody ever
370.
by aappleby 4y ago
I don't _feel_ like my working memory is particularly large, but that's also a hopelessly subjective assessment. Maybe it's more like my working memory can hold more things by aggressively discarding details until I need them
371.
by aappleby 4y ago
I think I would get lost, but only due to the vocabulary and translation load and the "once" restrictions - not due to the content of the article itself. In practice I end up reading the same wiki articles dozens of times as I go
372.
by aappleby 4y ago
That's the thing though, I never get "lost". I've never studied quantum mechanics aside from snippets I picked up through pop science articles or such, so it's not like I started with a big body of knowledge already
373.
by aappleby 4y ago
I did the exercise mentioned and was happily bouncing around between 3 and 6 levels deep in Wikipedia before I thought I should come back to the article to see what else it said, at which point I became very confused. Perhaps "comforta
374.
by aappleby 4y ago
Reasonable, but it's literally the first point the article makes. Of the fraction of commenters that did actually read the article, I still would've expected at least a few to object.
375.
by aappleby 4y ago
Copy-pasting my top-level comment: I am utterly baffled that no response in this thread so far has taken issue with the statement "As you probably know intuitively, it won't work." For me, this _does_ work and I have proven i
376.
by aappleby 4y ago
I am utterly baffled that no response in this thread so far has taken issue with the statement "As you probably know intuitively, it won't work." For me, this _does_ work and I have proven it many many times over the years by
377.
by aappleby 4y ago
No, not anywhere remotely similar except that some of the terminology like display lists (that predated PS2) are still used.
378.
by aappleby 4y ago
Game Cube worked in 2x2 blocks of pixels and could also run primitive "shaders" by cycling a pixel block through the pipeline multiple times with different settings. Made for some nice bump mapping demos but I'm not sure how
379.
by aappleby 4y ago
Random trivia - the PS2 processed pixels in 8x2 blocks (no texture) or 8x1 blocks (texture) - this made rasterization VERY FAST for large untextured triangles (16 pixels/clock, potentially 4x Game Cube fill rate), but slow for tiny tex
380.
by aappleby 4y ago
You're not a graphics programmer, are you?
381.
by aappleby 4y ago
Parsec, I think?
382.
by aappleby 4y ago
... did you even read the code of conduct?
383.
by aappleby 4y ago
Programming languages are serialization formats for source code.
384.
by aappleby 4y ago
The pasta absurdity obscures the author's attempt at communication.
385.
by aappleby 4y ago
I would say that you can't use the simplified cable markings unless your cable supports the full set of features implied by the marking - if your cable says "20G", it must support 4k60 * 1. If it says "40G", it must
386.
by aappleby 4y ago
I propose we ignore the current names and just go with "USB-C 40G 100W" or "USB-A 5G 10W" or whatever. The current naming is silly and unhelpful.
387.
by aappleby 4y ago
No single thing, but in general the gradually declining fraction of people capable of understanding complex systems "from top to bottom" concerns me. I have seen far too many projects become locally-smart but globally-incoherent d
388.
by aappleby 4y ago
Plaintext is a serialization format for source code.
389.
by aappleby 4y ago
Plaintext is a serialization format for source code.
390.
by aappleby 4y ago
It's not that new, and in practice there aren't very many ways for it to get warty because it's basically a dependency graph with "run this command line if this node is dirty" attached to the edges. I like it very m

More ›