aappleby

On "just" a RTX 6000 Pro? You mean one of those $16,000 gpus?

You don't actually have to do this - you can stick with a power of 2 sized table and just gently mix the hash value to get each additional bit index.

(source - I wrote MurmurHash/SMHasher and have used the above in my own bloom filters and cuckoo hash tables)

Confit or cassoulet.

No. Tesla's resonance theory has nothing to do with dark matter, consciousness, or living matter.

just another ai slop project with no actual research

There's nothing real in that repo, just a 20k python file and bits of documentation - all AI generated.

There's a tiny cat on one of the roofs in Raissa! The rats in Marozia hop along their paths! The center of Theodora has bookshelves with individual books!

Even as I was writing this I kept finding more things I didn't notice on my first few passes through the cities:

Phyllis fades from color to black and white except for two houses. The fairground has a big top with tiny bleachers and a guy inside. The happy city has people with their arms raised in a V. People in the marketplace city wear hats and some are carrying bundles on their heads. There are weird cactus plants in the hanging city. In the half-fairgroud city, there's a statue on one of the trucks. The city that copies the dead has a set of pallbearers carrying a wrapped corpse down the stairs. The people on top of Argia are laying with their ears to the ground, listening for the animated sound waves coming from below.

And on and on and on and on. I just can't even.

First off - I'm a senior dev with ~30 years of experience in graphics engines, game dev, web dev, WebGL stuff, blah blah. I am generally skeptical of AI, but... after reading the top of every thread in this comment section, I feel like people forgot that they could zoom in on the cities to see all the details.

The amount of _stuff_ crammed into each little city is almost unbelievable. Drawbridges open and close, glowing lines sketch patterns, camels walk across a tiny desert. Buildings fade into existence and then burst in a shower of sparks. Flags fly, smoke drifts, buckets cause ripples as they dip into underground pools. The city made of plumbing has tiny people in the bathtubs! There's a freakin' roller coaster with moving cars and a ferris wheel!

I absolutely understand the AI hate that's being commented here, but... in this instance, I just can't feel it. I keep finding more and more little details every time I click on a city, and I am astounded. I just now noticed there's a little guy in the city of strings hanging up new strings at the top of the hill. Damn. My favorite is Marozia, where dark buildings open like treasure chests and release shining towers and flocks of glowing birds.

Yes, there are also a lot of stupid AI errors - every spoked wheel has the spokes off-center for example. But holy crap, I just can't hate this. I don't care about who built it or the random bits of jank - this thing is _beautiful_ in a way that I haven't seen from AI before, and it warms my old GPU-powered heart.

Based on some of the entries in there (like a list of the test equipment in my office), it's clearly scraping my public Reddit posts.

I have always phrased this as "Never do one of something".

Uh, no? Is this even a question? Is this hacker-relevant?

Ah nostalgia. I started in the games industry doing N64 programming, and our devkits looked similar to those flash carts but there was a big SCSI cable connector that went to the host PC.

Later on we had some "debug" cartridges that sat in between the console and a flash cartridge and intercepted reads/writes to a single address and replaced the data with whatever came in over a serial port back to the PC. That was enough of a backdoor to implement very basic dynamic reloading of art assets - I wrote a Photoshop plugin that added a "send to N64" button and some game-side support code and the cycle time for artists trying to see their work on a TV went from 30 minutes to 10 seconds.

FWIW, if you start with "The view frustum is a 90 degree pyramid with the tip cut off at z = 1 and the 'end' at infinity", you can then work out how to map that to a NDC using a matrix and perspective divide.

I've used that when teaching short "Graphics 101" (not in the first session though) and the math comes out more intuitive than the usual "here's how to calculate a perspective matrix, don't ask where these numbers come from" version.

anyone who thinks "woke" is a valid counterargument is not worth listening to.

yep

I have a whole thread over on Reddit about it, the spec sheet is wrong - but you must use displayport.

and he's been complaining ever since they stopped letting him shoot machine guns at teddy bears.

One of the interesting things about the N100 line of chips is that they can drive a 4k120hz display just fine - which is _awesome_ for game streaming.

Looks like the next gen is gonna ditch that. :/

Arduino doesn't know who they are anymore.

Fun fact - Google Maps does something similar to this in WebGL in order to keep accurate coordinates across a planet-sized map using only 32-bit floats.

You want "Onboard Memory Manager", which is 12 megs.

I use this all the time, works great.

It has an effect only in terms of how big an offset you can encode in a relative jump, the _arrangement_ of those bits in the instruction is irrelevant (and already abstracted away in the compiler/linker framework).

Having written a few RISC-V cores, worked on a chip design project that used RISC-V cores, and generally being OK with the architecture in real-world use cases:

What the heck is this guy's problem? Just about every thing he mentioned as a problem is not a problem in practice. Too many options? Who cares, you're not trying to write code that runs on every possible configuration. Either you're writing embedded firmware and know exactly what core you're using, or you're writing an application that runs in an operating system and that system has a minimum ABI like RVA20 or whatever.

Array accesses take an extra instruction? Either you're in a tight loop walking a tiny array and you don't do the full offset calculation per step, or you're walking over an array in RAM and you're bottlenecked by the memory bus.

Hell, 90% of his arguments are "You can't detect X at runtime from user code without relying on some extension" - Yes, that is totally fine. Either you know your target CPU, or you don't - and then you ask your OS for details. This is not some dealbreaker.

From the article - "For example, if you are writing a kernel and want it to support all RISC-V cores" - NOBODY IS DOING THAT. You target a platform spec, not the combinatorial explosion of everything from RV32E to RVA22 or whatever the latest is.

You want to distinguish S mode from M mode? WHY DO YOU NOT ALREADY KNOW THIS?

Instruction encoding is weird? WHO CARES, the decoding is like eight lines of Verilog.

"Who can predict how their binary will act when a floating point store silently becomes a double-register move or a jump instruction, or vice-versa?" - THIS DOES NOT HAPPEN IN PRACTICE.

Guhhhhh, I don't get it. This guy has some vendetta and either has not shipped any risc-v code or is just in love with his own personal favorite instruction set.

I have a B70, what llama options are you using and what performance are you seeing?

So what do you use for debugging?

I've had tinnitus for 25+ years after neglecting an ear infection while I was working overtime.

It's never disappeared, but the "rain on a tent" sounds from mynoise.net, fan noise, and having a Twitch stream on in the background masks it enough that it's not bothersome during the day.

"Befriending" it though? Naah, I don't think so.

I reverse engineered the Game Boy from pictures of the die - https://github.com/aappleby/metroboy - so yes, it's totally doable. It is also incredibly tedious and frustrating.

Not sure if that gives me an advantage in this challenge, but I have too many things to do already. :D

If this is "simple", then I don't think the author has tried a good parser combinator library yet.