I had a discussion with @stsp at #36c3 about using got for #HamBSD development. Instead of manually maintaining a patch set alongside the src.git fork, the plan will now be to archive the old HEAD of branches in refs/archives/master/YYYYMMddThhmmss just before finishing a rebase.
This means that the objects will stick around and not get garbage collected. You wouldn’t pull these by default, but you could if you wanted to. You can also diff objects with previous versions of objects across rebases.
I just spent a couple of hours hacking on this, but so far all I have working is making sure that the arrangement of options for got rebase is sound. I need to work out which of the many references is the one I want to archive, and work out how to find that even when continuing a rebase after fixing conflicts.
I never realised there was a way of learning Morse code in such a visual way https://www.cryptomuseum.com/radio/morse/
femininity and masculinity are individually perceived concepts. We may be told by others what they think it means, but that doesn't mean we have to agree with them, or that it's the one truth.
It's simply a vague set of ways you show yourself to others.
they are not intrinsic to anything, certainly not some fixed set of body types or behaviors.
Therefore terms like "lesbian" don't really mean anything at all.
So we can either get rid of them, and make new ones, or, shut the fuck up about them.
Because just because you don't perceive someone to match your idea of what lesbian means, doesn't mean they don't.
Because someone asked:
Yes, matter of fact I do want to completely abolish gender as a concept, and get rid of terms of gendered attraction
Because they are entirely obsoleted artifacts from a time when we considered gender to be much more strictly binary, and these terms made sense. They no longer do.
So, I would much prefer we create new frameworks and terms to describe personal expression, and sexual and/or romantic attractions.
The entire concept of "masculine" and "feminine" gets tossed out, and instead we should focus on attributes that are entirely independent of one's physiological build, which is essentially what we're already doing by adding all these new "edge cases" to our legacy model.
Ncurses is garbage, rant
Ncurses ONLY reads ONE format OR the other.
Meaning, if you compiled ncurses with the short number format, you're stuck with that.
So I browsed the code for a while, and looked for the compile time conditional for it
Okay, maybe I missed a configure flag.
Okay, let's grep the entire fucking directory for it.
Extended Number Support, requires Extended Color Support, which requires Wide Character Support.
Even though I used the exact same configure flags as last time, this time it actually fucking worked
So, built everything, installed it, ran tic, and there's my fucking extended number format.
So now, direct color support will actually fucking work.
re: Ncurses is garbage, rant
@steph there's no fucking reason why this shouldn't work without compile time conditionals anyway
the magic for extended number terminfos is DIFFERENT, and terminfo already uses 32 bit ints everywhere internally
the only reason is bullshit legacy
we really need to deprecate ncurses somehow.
3rd time on first year of Informatics undergrad
• ❤️ pureneß in Functional Programming
• DM open
• p.a.k.a. ArchieT
functional.cafe is an instance for people interested in functional programming and languages.