kjeetgill

Depending on what your working on, it's actually super nice to know very clearly what lives on the stack vs the heap for performance and compactness reasons. Basically anything that didn't come from malloc or a function calling malloc lives on the stack and doesn't live past the function it was allocated in.

And these days, if you're bothering with C you probably care about these things. Accidentally promoting from the stack to the heap would be annoying.

I'm pretty soft on this subject but one thing that's always bugged me when I see bivectors represented as a parallelograms is that different coplanar parallelograms of the same area are the same bivector algebraically but visually very different. It just feels confusing when you're trying to learn what it "is".

Aren't we talking about Waymo? It's not perfect everywhere but it's definitely already better than most people driving around SF. That's pretty full to me.

I guess they haven't been allowed on freeways yet?

I mirror the previous posters experience: the Waymos drive better than a good amount of people I know and to the the best of my knowledge haven't had any issues with pedestrians except being attacked by them once or twice.

So I'm not sure what you're referring to? Did I miss a story?

Because the parent-most post from quertox was:

> That's great news! I thought the project had died and that this meant that V8 was the only serious JavaScript engine for the future.

The person you're responding to was basically clarifying what you want to too.

The free non-logged in chatGPT didn't produce an answer for either for me.

Stripping out Maps/Lists with boxed keys and values is the first easy thing to do when perf tuning a piece of code. It's so frequently impactful that it's worth doing immediately without any measurement.

You just swap them out with fastutils or trove and call it a day.