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.

Unfortunate typo. I assume you meant ethnically not ethically.

The poster is basically proposing something like always doing:

  def all(lis: List[T], mapf: Callable [[T], bool]) -> bool:
    for e in (mapf(l) for l in lis):
       if e is False: return False
    return True

At least that's my take on avoiding Truthy and Falsy via a mapping closure (or function?). But I don't see it solving OPs issue here when lis is empty... So maybe I'm missing something too.

I'm totally with you for processes should probably use glibc/platform API calls, but procfs is nothing short of brilliant and a great validation of the power of the "everything is a file".

I'm not sure that's the case. I don't think people are responding to the "redneck in a pick-up" stereotypes as much as that "pavement princess" owner trying to "cosplay" truck culture stereotypes.

Sidenote - I'm finding my vocabulary pretty lacking now that so much stereotyping is done in images and memes.

Huh, TIL - though

> A tree which is not rooted is sometimes called a free tree, although the unqualified term "tree" generally refers to a free tree.

I wonder if that was once the case but no longer is. I'm learning I think of trees mostly through the lens of data structures and not graph theory and I imagine more people do than not.

Tree's are subsets of DAGs — A DAG where each node has a single parent except for a specific root element which has none.

Not OP but between Java and C# it's hard to not to lean Java for the absolutely massive lead in high quality libraries and ecosystem support. C# still feels like the new kid in open source circles though the languages are 90% the same.

Probably a cheeky response but certainly!

We can say most positive integers are greater than 5. Or most real numbers are irrational. Half of all integers are even — even though there's just as many of both!

I haven't heard about this, can you elaborate on this?

Vore's comment was critical of revskill's comment that was just ChatGPT output — not your article.

Maybe you can't see dead comments?

A ton of comments are missing the point of this complaining about list/map syntax etc. I'm not sure if the kotlin lazy addresses this.

The point is that static final variables interact especially well with the JIT's constant folding machinery. But lazy loading a constant necessitates that it can't be final: it's initially null until it's effectively final after the first lazy load. This finality is clear to the developer but not to the JVM.

This is introduces a way to implement lazy constants via a blessed class that solves this.

The article is pretty clear about what the point is — but does require some careful reading and context.

I'm not sure if we're taking about different time periods, but weren't they at the forefront of chariot warfare during the bronze age?

And I vaguely recall that inventing bellows to melt iron took a long time too, so steam machinery seems pretty far off if all you have is bronze and stone.

Don't quote me, but I think the name isn't meant to be SQL-lite but SQL-ite with the suffix meaning rock/stone.

Iirc, I think in this case it was more ageist than racist in practice, but point stands.

I assume you meant "fake != 1"?

So I've heard this a lot. Am I the only one who found jq to be fairly sensible and intuitive?

I'm not saying I don't need to pull up the docs once or twice for regex or leafpaths (or was it leaf_paths, lol), but overall I can't think of something that needs to be pulled into the standard install more. It's near perfect.

I think it's one of those distinction people are trying to impose on the words rather than how they've always been used.

I think there's a popular blog post that kicked it off.

Nothing alike. Texas had it's independence on it's own for 10 years before becoming a state.

Russia invaded Crimea and annexed it in months — about 9 years ago.

Nothing alike. Texas had it's independence on it's own well before trying to become a state.

Some people just actually pronounce it as Mastadon over Mastodon.

I don't know if it counts, but you could compile it down to llvm bitcode and run it on sulong as a part of graalvm. I imagine it comes with caveats but it's used for real stuff.

I hate to be a naysayer, but if you really want something like this -- just use ipython.

You can put any python you want in a file and run $ipython -i main.py and it'll drop you in a shell with whatever you want in scope. It can load configs from your ~/config directory, have a command line history, use tab completion, and you can the full language to compose those operations and inspect your results.

Weak take. No one's saying, "Need a Calculator? Nah, just use ChatGPT!". That's how you flounder in local optima.

This is just line of inquiry that's a part of any research. The Wright Brother weren't solving "real" problems like passenger transport or mail delivery initially. They had better solutions. It was to see if they could get the thing to fly.

edit: Before it comes up, I'm not saying it was for lulz. I'm sure they had commercial considerations. Just that those problems had "right tools for the job" for a good while.