2,080 karma · joined May 20, 2024
Seems like a typo when covering inversion. They claim parity(0) = 0 but still use the equation with != from before.
It's nice to see that they, like me, subscribe to "an hour of experimenting can save 5 minutes of reading the documentation." Of course what people often fail to realize is that until you've found the answer, you often don't realize what the documentation was saying, such as the 16-bit thing. Management may ask "was that not in the manual?" But it's more nebulous than that.
Arguably you could say that in the days of the monarchy we only had 1 person, the king, controlling our culture. And I'm sure there's influence. But at least personally I've never heard anyone hold that viewpoint.
> I would UDP joke tell you a… but you get it might not.
Edit to add: I do not mean the GPS satellites or the starlink ground terminals. That was not the question so that is not my answer. I mean the starlink satellites
#1 and #2 are fixes for breaking that implicit trust. #1 still trusts the metadata, #2 is what I'd consider the most robust solution is that not only is it ideally trivial (just compare if a pointer is within a range, assuming zig can do that) but it doesn't rely on metadata being correct. #3 prevents the desync.
I really don't understand the code base enough to say definitively that my ways work, which is I guess what I'm really looking for feedback on. Looking at the memorypool, I think you're right that my assumption of it being a simple contiguous array was incorrect.
ETA: I think I'm actually very wrong for #2. Color me surprised that the zig memory pool allocated each item separately instead of as one big block. Feels like a waste, but I'm sure they have their reasons. That's addCapacity in memory_pool.zig
23 minutes later I'm at +2
6 minutes after, +5 +4min now +6, another 20 minutes +8. I think I'm in the clear
I don't understand why that is the preferred fix. I would have solved it other ways:
1. When resizing the page, leave some flag of how it was allocated. This tagging is commonly done as the always 0 bits in size or address fields to save space.
2. Since the pool is a known size of contiguous memory, check if the memory to be freed is within that range
3. Make the size immutable. If you want to realloc, go for it, and have the memory manager handle that boundary for you.
Both of those not only maintain functionality which seems to have been lost with the feature reduction but also are more future proof to any other changes in size.
You: "I would like to remove blurry frames with ffmpeg. I think I want to use xyz method. Can anybody please help me craft the command?"
Them: "yes, here's the command" (and maybe it's exactly what the LLM output)
You: "it's giving this error code. Here's a snippet of my input file. Can you please check if that works on your end?"
Them: "oh wow you're absolutely right, this doesn't work, I'll put in the issue ticket"
This is a lot nicer than "something else told me how to use your tool and it's broken".