snthpy

Evolutionary temporal variation is addressed in the article. Although that could just say that without bipedalism, the pressure to use the hands to climb forces equal use over the available hands.

Interesting. Does this then become informative about the level of cooperation vs competition in the population?

In ping-pong where it is pure competition it stabilises at 50:50. In everyday life where we largely collaborate it settles around 90:10.

Would be interesting to see if there are variations over populations in time or space with differing levels of competition/conflict. Ofc these would need to persist long enough for the populations to adjust.

P.S. This is probably just another plausible sounding evo-psych bs theory. Idk why people give AI such a hard time for hallucinations. We are just the same. I guess we generally just apply more filters before expressing ourselves publicly. The problem with AI content is that humans take it at face value and publish without scrutiny.

> Let me repeat that: You had to take a class. And pass an exam. To be able to apply to host a college party.

Jeepers

I agree. A good read overall as well.

OT but anyone remember Diaspora? Which was supposed to be an open (source? Idr) FB. Never heard of it again after the manifesto post.

I like it but confusing that there's also a similar but different loonlang.org.

I agree. I've switched to pls and tx just for my own typing because of how common they are.

> We found that high-quality constitutional documents combined with fictional stories portraying an aligned AI can reduce agentic misalignment by more than a factor of three despite being unrelated to the evaluation scenario.

tl;dr Fairy Tales are an effective teaching tool in vivo et in silico

Aha interesting. Thanks!

Looks cool.

That's kind of my (not the project's) vision for PRQL - a general LINQ type embeddable data transformation language.

Unfortunately no time to work on it these days.

YAML no thanks.

I want something that uses BPML for actual business workflows.

Thank you. I also did a double take and concluded this must be about arm64 emulation then.

A bit OT but what about the Netherlands?

As PoW goes, this is cool.

One thing I didn't understand though is Light mode:

> Fast mode is for mining. Light mode is for verification. The reference README says

The post only describes Fast mode, right?

Presumably verification is done by miners who already have the memory set up so Fast mode would be faster for them.

Verification is still relatively fast because you don't have to try gazillions of nonces so who is Light mode necessary and how does it work?

Yeah like the rhinos and elephants that I didn't know you used to get in that area. Maybe they were too efficient and that's what limited their proliferation when they hit resource limits?

Good question! Idk and I don't make the rules. I guess people default to it because most people have git installed already?

I'm thinking of LazyVim for example which has [1]:

    git clone https://github.com/LazyVim/starter ~/.config/nvim

After that, once you do a sync or update, there's a whole lot more cloning going on.

The other projects I was going to mention have apparently all switched away from using git for their package management (homebrew, Go, cargo, ...). I can't help but wonder to what extent that might have been influenced by the default slowness of doing a full git clone?

Of course these all could add `--depth 1` to their instructions or internal package management tooling, and ofc we need both options to be available. I pondering aloud that in my observation, `--depth 1` is probably the option that I want more often than not but YMMV.

1: https://github.com/aerys/gpm

Thanks. Makes sense

Fair enough. I also work with a monorepo at work but that I cloned like 5 years ago.

If I think about what I've cloned over the last week or so (LazyVim, gstack, my dotfiles), most of the time I just want the current state and be able to pull updates. Even for my dotfiles or projects that I fork and hack on, most of the time I'm just adding commits and it's seldom that I want to go back to historical ones.

Given how often I see `git clone ...` instructions in Github README.md files, I was just wondering how many other people felt the same?

So my contention is that most of the time, `git clone --depth 1` or `git clone --filter=blob:none` is what you actually want, and in the case that you want the full history then you could do `git clone --depth 0` (or `git clone -full` for even better UX, not that the git cli is known for it's UX).

Thanks. That's great! I especially like that it then lazy loads the blobs as you need them.

I was going to ask if there's a way to set that as the default but I guess I'll just set up an alias like I have for most of the subcommands I use daily.

I've been wanting to ask this:

Why isn't

    git clone --depth 1 ... 

the default?

I would guess that for at least 90% of the repos I clone, I just want to install something. Even for the rest, I might hack on the code but seldom look into the history. If I do then I could do a `git fetch` at that point and save the bandwidth and disk space the rest of the time.

This is a good point and imo there is an interesting tension between adaptability and specialization.

Stable environments naturally drive populations towards more specialized actors in niches as they benefit from efficiency. Think of leverage in the financial economy or the dinosaurs.

When a big system disruption inevitably arrives, you better hope you still have some depth around with adaptable general populations that can survive the crisis and occupy the new environment. Think of Minsky moments and the K-Pg event for the dinosaurs 66 million years ago.

Another example would be stem cells vs organs and their specialized cell types.

It seems to me like you need enough regular change to avoid overspecialization and preserve the ability to survive large changes.

This is how future codebases will be analysed. Don't let perfect be the enemy of good. Evolution been doing Agile for aeons. Responding to change over following a plan ...

And they use SHA-1 for verification?

I couldn't make out the 1x5 properly but the 2x5 was totally readable.

Ah you're right, thanks.

Another aspect which was too long for me to type on my phone earlier is that debt/Schuld is backward looking while liability/Pflicht is forward looking.

So while debt is incurred through past actions, what matters from an operational business perspective is your liability, i.e. your obligation for future payments/value transfers.

In english speaking business practice, debt and liability seemt to be used interchangeably. I have never used German in a professional setting and am only familiar with the colloquial usage of Schuld and Pflicht so I would be interested to hear how those differences play out in German business use.

Yes, I can't get snap to work on unprivileged LXC on arm64.

Good points.

I think that liability may be the better analog for Schuld as it also has the liable<=>schuldig form and carries more of the connotation of guilt.

Does that mean that we're likely to see Mythos released soon?

TIL

Thanks. I've tried it and I'm a convert.

I think part of my resistance initially was that it took up much screen space with borders and such. I learned now that that can be switched off or modified. Didn't go deep yet, just tried the different options from `zellij -l welcome`. I think that should actually be the default startup and then maybe disable or prompt to disable in future.