jesse__

48 ms·

391.
by jesse__ 4y ago
Generally I agree, but have one big disagreement with those statements. >> It's much simpler to just mark fields as private with some convention. If callers want to muck with your struct, they will. Agreed, and people mucking wit
392.
by jesse__ 4y ago
>> My own approach to C metaprogramming involves obtuse preprocessor hacks I considered doing this, albeit briefly, but decided against it for two reasons: 1) I hate the preprocessor. 2) I found a few projects that did that already. U
393.
by jesse__ 4y ago
>> The disadvantage is that users can’t control how the structs are allocated Yeah, that usually kills that plan for me. I also try to avoid heap allocation wherever possible (which is usually pretty easy), and that solution ends up
394.
by jesse__ 4y ago
Can you elaborate slightly on how you're planning on using _Generic to turn runtime dispatches into compile time ones? I'm not quite putting together how you can do that.
395.
by jesse__ 4y ago
0MgZz yea PDF has got to be one of the worst specs ever created. It's amazing PDF viewers work at all.
396.
by jesse__ 4y ago
I've done a few APIs similar in spirit to this one (and one similar in functionality, too), and I've found using a blend of a few of the mentioned methods to be pretty effective. I start with the basics and implement everything as
397.
by jesse__ 4y ago
It wouldn't matter if the DOM layout engine ran on a separate thread, but it runs on the main thread, so it blocks your games update loop for a few frames every time you shoot, or whatever. Now, that's not to say it has to be that
398.
by jesse__ 4y ago
From personal experience, if you're trying to make a game that cares about its frame rate, do not ever use the DOM for anything, ever. It routinely takes several frames to layout a single absolutely positioned element. I recommend the
399.
by jesse__ 4y ago
Why exactly would programs running in web browsers not want the ability to access the most powerful piece of hardware in a users machine? WGPU unlocks an enormous amount of space for userland programs to explore. I agree there have been so
400.
by jesse__ 4y ago
I think it depends, but given an arbitrary compute pipeline, you should be able to write the results (or intermediary results) to the screen with minimal effort.
401.
by jesse__ 4y ago
Oh my gosh, the future is now.
402.
by jesse__ 4y ago
Nicely polished, I like it. EDIT: Turns out the following behavior is intentional, but I'll leave the statement here so the child comments make sense. I wanted to point out what may be a bug .. if I quickly drag a face-down card off th
403.
by jesse__ 4y ago
This bug would suggest that ETW is actually the giant pile of shit. Which, in my experience, isn't far from the truth. Other people think so too: https://caseymuratori.com/blog_0025
404.
by jesse__ 4y ago
I'd love if you'd elaborate on this. I know very little about what VirtualProtect actually does under the hood but, in theory, it should just have to flip a couple bits in the address space mapping which says what the protection
405.
by jesse__ 4y ago
There's nothing about the bug that had anything to do with malware protection, or branch prediction, so I'm not sure how that statement applies to the conversation. The bug was in ETW, which just happened to surface in a windows u
406.
by jesse__ 4y ago
I'm not sure how you can possibly qualify VirtualProtect as "an expensive platform feature". Looking at the operation that VirtualProtect actually has to perform, from first principals, it should be one of the cheapest sysca
407.
by jesse__ 4y ago
I was thinking more in terms of behavioral characteristics, as your edit suggests. In my mind, a strictly 'P' controller should produce an oscillation, which the example did not. I then surmised it 'hides' the 'D&#
408.
by jesse__ 4y ago
Not trying to be controversial, but I'm curious why you make the claim this is not a PD controller; I thought this is basically a canonical example of one. Could you shed some light on the specific reason this does not qualify as a PD
409.
by jesse__ 4y ago
Sorry, that was a comically ambiguous statement. Taylor (surprisetalk) also submitted article [3] to HN today, and wrote neither. The irony I saw is that article [3] linked above directly addresses the shortcomings of the article discussed
410.
by jesse__ 4y ago
Ironically, the person who posted this article on lerp also posted the article you linked to in [3], which calls out exactly the problem with this article. What a weird series of events..
411.
by jesse__ 4y ago
I believe this is actually an example of what's known as a "proportional derivative controller", which is effectively an underdamped spring. With a PD controller, the further the target points are apart, the faster the inter
412.
by jesse__ 4y ago
dang, that's a lot of karma
413.
by jesse__ 4y ago
I think reducing this to "using mmap is basic" is pretty unfair. The trick she did overriding malloc & friends to validate that the optimization would be worth doing is, in my mind, one of the high-points of the paper. It&#x2
414.
by jesse__ 4y ago
HAHAHAHAHAHA The accuracy of this statement just tickles me
415.
by jesse__ 4y ago
I'm working on a team that's >50% 30+ year career engineers. It's the best team I've ever worked on by an enormous margin. I don't know how many dollars any of them spent on education, but I know everyone I work
416.
by jesse__ 4y ago
UPDATE: After a nominal amount of googling around it appears valid sizes have increased on 64-bit systems to a maximum of 8GB, and stayed at 2GB on 32-bit systems, for FF at least. I guess it's probably 'implementation defined&#x
417.
by jesse__ 4y ago
WASM is specified to have 32-bit pointers, which is 4GB. AFAIK browser implementations respect that (when I did some nominal testing a couple years ago)
418.
by jesse__ 4y ago
I thought the memory limit (in V8 at least) was 2GB due to the GC not wanting to pass 64 bit pointers around, and using the high bit of a 32-bit offset for .. something I now forget ..? Do you have a source showing a JS runtime with a 1GB l
419.
by jesse__ 4y ago
I can't remember which studio (maybe naughty dog), but I remember a story from the 90s of a studio who forced their developers to work on minimum spec workstations during development, with the theory that it would ferret out costly per
420.
by jesse__ 4y ago
>> you just get hit with the ill-quoted premature optimization line Frankly, if someone says that to you and they're not shipping software that runs locked at 60fps, fuck them.

More ›