Notices by Luke T. Shumaker (lukeshu@fosstodon.org)

@evan "No, but" I'm just an ally (so my opinion on inclusiveness shouldn't be given much weight) and one who isn't even that great with people (so my opinion on how important pronounceability is shouldn't be given much weight).

I've seen several variations w/ "2S" somewhere in there; the inclusiveness is not adequate.

"LGBT" wasn't great w/ pronouncability to start with, and doubling the number of syllables is… a lot.

Enumeration is a losing strategy on both fronts.

@cmccullough A lot of folks knew PHP when it was a truly terrible language, moved on to better languages, and then missed PHP getting good.

PHP 5.3 (2009) is when PHP started to get good, and it's improved so much since then.

Before 5.3, PHP very much felt like a terrible hack that *knew* it was a terrible hack but was well-maintained and fast anyway because a few important folks made the mistake of putting it into production. With 5.3, it started evolving toward a well-designed language.

@LucasWerkmeister The alt-text describing the stripes, but not why they're wrong, is DEVIOUS. ❤️

Oh heck yeah {} initializers are valid in C23 and not a GCC extension anymore.

The pagefaulting instruction is

0x80001255: 0f a9 popl %gs

At first I was thinking "it's just a pop; how in the world could the stack have gotten paged out!?" and "`qemu -d mem` says there aren't any mmu operations between the corresponding `pushl` and that popl".

But CR2=000004c0, and that neither looks like a stack address nor looks much like SP=0008:80064c08.

Ahh, GS is a register related to segmented memory; GS=04c7.

I don't want to learn segmented memory :(

Oh, ok, INT=0x18-0x1F are the first 8259 PIC, and #Plan9 programs it such that INT=0x18 is the clock interrupt.

So a INT=0x18 (which is supposed to be reserved???) is happening inside of runproc(), but then a INT=0x0e pagefault happens inside of intrcommon, and then a pagefault happens inside of fault386(), and then a pagefault happens inside of fault386(), and that recurses ~2000 times with the stack growing each time until it overflows all the way into the text area.

#Plan9 #RetroComputing

So somehow I didn't know about #qemu `-d in_asm`, which is letting me finally make progress on figuring out why #Plan9 1e for PC is crashing .

So far:
- "0x800012c6: 00 80 0e 00 00 00 addb %al, 0xe(%eax)": that's not the instructions at that address, it must be getting overwritten
- a few gdb watchpoints later: %sp is getting set to in the code area, so "benign" instructions are corrupting things.

Now to figure out how %sp is getting messed up.

#RetroComputing #ReverseEngineering

"Company doing unethical thing says they will leave state if law banning unethical thing passes."

Um, good? That's the point?

I feel like there's room for "C, but with less jank" without getting in to "better C" (Rust, Go, D, C++?).

Have (un)int{n}_t be the primitive types, instead of long/short and guessing what they mean. Integer promotion rules that make sense (what insanity it is that short+short=>short, short+lit=>short, but short+lit+short=>int).

@evan
2) I remember a Governor race where both candidates had *incredibly* similar platforms, with the main difference being that the D had detailed financial documents about how he was going to pay for it without raising taxes, while the R said "idk how I'm going to pay for it, I'll probably have to raise taxes". Yet I'd near-constantly hear people saying that they were voting R because they didn't want their taxes to go up. The standard "party position" was inaccurate for this race.

@evan (I selected "Mix")

"By party" answers really frustrate me, because:

Where I'm from (Indiana):

1) With the way the state D party runs, it's all but impossible to primary against an incumbent D. So you if the D is running for reelection, but you think they're doing a shit job, the most realistic thing to do is run as an R. (I imagine the converse is true too, but am not familiar with how the state R party is run.)

@hyperreal "Venturing outside one's comfort zone can be instructive, if only to make the return that much more comforting."

Trying other ways of doing things is good, if just to be exposed to new ideas. Once at work I forced myself to use Vim for a month (I allowed myself to still use Emacs at home). Get to actually be proficient with it, so I can have informed opinions about it.

Futzing with Acme has been informative about some interesting ideas that I want to bring back to Emacs.

I've been refreshing a news search for "van hollen" all morning.

He's currently giving remarks live: https://thehill.com/video-clips/5252080-watch-live-chris-van-hollen-kilmar-abrego-garcia-el-salvador/

In my mind, there's no way that what Van Hollen sees doesn't cause change.

"I think you eat demons in your sleep."

ok but why is the green skittle lime but the green gummy skittle is green apple

"reliable bidirectional in-order octet stream" is such a good abstraction (eg: TCP is an instance of the abstraction), it's flabbergasting when it isn't used (eg: Linux fs/v9fs/trans_*.c).

@martinl @BryanBennett Yeah, an IP-KVM or BMC/IPMI is the answer.

Decent options right now are PiKVM, JetKVM, Sipeed NanoKVM, TinyPilot KVM.

#9P has DMEXCL/QTEXCL for files that may be opened by only 1 client at a time. But I feel that it would benefit from DMWEXCL for files that can have any number of readers, but opening it with write access requires it be exclusive. Like #GoLang sync.RWMutex vs sync.Mutex.

#Plan9

@my_actual_brain Same story of Oracle pissing off Sun's volunteers and the volunteers continuing with a new name for OpenOffice→LibreOffice (except that the original creator hasn't been involved since ~1999).