aib

*in the U.S.

Did you steal my idea of Human-to-Trasformer Protocol??

That work like this often predicts a good portion of the technological advancements, but usually completely misses the mark on the execution and the enshittified commodification is why I like reading cyberpunk and other dystopian sci-fi.

My default pull is ff-only. I don't like merging or rebasing by default.

When working in a short-lived branch, I like to rebase. I usually get no or simply easy-to-solve conflicts. I like my small and numerous commits stacked on top of the current develop. Regardless or whether we squash or not.

For long-lived branches (and technically for hard merges, though I've been using rerere more and more) merge is a better option.

What kills bisect, IMO, is large commits or commits with multiple subjects/goals. That's the reason I don't like squashed PRs.

You're absolutely correct! </s>

The "how to modify an environment variable" bit and the bin-dec-hex table made me feel the same way. Then I saw the part explaining how to check for duplicates in a row... I'm struggling to understand the point of the article. Testing a text generator?

One more from me:

  mkcd() {
    mkdir -p -- "$1" &&
    cd -- "$1"
  }

Most input is text, most output is text, commands are text. Vast majority of programming languages can process and produce text out-of-the-box. There are countless utilities for processing text. You can store, load, split and join text easily. Send and receive it through most channels.

When everything is text, text files become libraries. Text editors become macro processors.

Just tried it on our codebase. Getting over a thousand errors, a good portion of which seem to be:

    ../../../tmp/typescript-go/built/local/lib.dom.d.ts:27982:6 - error TS2300: Duplicate identifier 'KeyType'.
    27982 type KeyType = "private" | "public" | "secret";
               ~~~~~~~

      ../../../tmp/typescript-go/built/local/lib.webworker.d.ts:9370:6 - 'KeyType' was also declared here.
        9370 type KeyType = "private" | "public" | "secret";
                  ~~~~~~~

Probably an easy fix.

Running it in another portion results in SIGSEGV with a bad/nil pointer defererence, which puts me in the camp of people questioning the choice of Go.

Exactly. They want _their_ oligarchs controlling their 99.(9)%. This ban is as close as you can get to open admittance.

(Not directed at the parent comment but the thread in general)

I don't know why people are more interested in labeling it than explaining it. (Although admittedly, they go side by side.)

Every grammatical aspect of "past time with -miş" (which is how I learned it) is the same as the other one, "past time with -di". As in, I cannot think of a sentence where replacing one suffix with the other would result in a syntax error, or any semantic difference other than certainty.

A point of confusion might be verbs made into adjectives using -miş, although I'm having a hard time coming up with many examples where there's an ambiguity between the adjective and the "tense". Doesn't help that the assertive(?) case is without suffix, so "pişmiş" might mean "[it is] [a] cooked [one]" or "[Apparently it was] cooked".

Another point of parallelism between the two past "tenses" is that it's perfectly valid to answer a question in one with the other. (Or is this a general language or tense thing? Hmm.)

Is there some sort of explanation of what DMNO is?

So: "Sleep on it" is an effective strategy.

A pain point, for me, is having to explicitly type private functions.

I like refactoring independent blocks out into functions, to separate the scopes and have readable summaries a la self-documenting code. Having to fish out and then explicitly enter some library's useful but complex type makes it unpleasant.

I'm starting to see a pattern here... Hmm, maybe private functions should be treated differently?