gomijacogeo

Over time, require trusted boot and a TPM. Require a signed age-verification cert to get tokens to access io devices and net. It feels like part of a long play to claw unregulated general purpose computing out of the hands of the masses. Or, at least, get as much as can be moved into the cloud which can be easily surveilled and shut down.

Assuming the jamming is coming from close to the horizon, I wonder if one could improvise a choke ring around the antenna with some sheet metal or foil.

No, they got rid of the load delay slot in MIPS II. While not required in later ABIs, they kept the branch delay slot for backwards compatibility. MIPS32/MIPS64, which came out much later, also had several new branch instructions without delay slots.

One (probably the only) nifty thing the branch delay slot allowed was in the user-space threads implementation, you didn't have to burn a register for the jump to another thread, you'd do the branch and then clobber the register with the last bit of the jumped-to thread's context. Kinda fiendishly clever.

The paper would be a lot less infamous if the title had more accurately been "A Texel is Not a Little Square".

99.9999999...% of 'everything' in the universe simply falls down a gravity gradient to be crushed into simple oblivion.

Lex Fridman interview with Lenat a few years back. https://www.youtube.com/watch?v=3wMKoSRbGVs

Good video with Harry Brodsky from CU Boulder talking about phosphorus availability around ocean vents. https://www.youtube.com/watch?v=Ppc3zzMTJTs

Anyone who buys Intel would probably be making the same mistake Boeing did with McDonnell Douglas.

Unlikely; the pilots are (correctly) following the approach controller's direction. It's approach's responsibility to keep them clear of other traffic. Also they just got handed a different runway to land on that's a lot shorter and in one of the more complex airspaces of the planet; they're busy.

His well over 6,000 word perspective.

And I think that's one of the reasons Kent got the pointy, if maladroit, end of the CoC's attention. Every time he wants to break/rearchitect an internal API, or every time he makes a submission that flagrantly goes against kernel convention, you have to navigate a dozen walls of text where Kent vents and re-re-relitigates every transgression he's endured, every minute detail of his thought process as to why he needs to break the rules because his case is special, his list of ailments and anxieties that all the pushback is causing him, etc, etc, etc. His language is frequently escalatory and he seems unable to contemplate alternatives until at the brink of someone's (frequently Linus') patience and threats of bans or having bcachefs yanked from the kernel. It's brinksmanship and he overstepped.

In short, he is the "that guy" on the list.

Upon further thought, the child can't inspect a parent's environment variables after forking, so my thinking of ^Z eval `resize`; fg can't be the way it worked. Maybe quit and restart vi was the only way back then. It's a been a while.

e.g. https://datatracker.ietf.org/doc/html/rfc1073

If you dig into the RFCs, you'll see that ssh and telnet can negotiate whether each end can send/receive out-of-band messages about changes to window size. If they both can, the client side gets a local SIGWINCH, turns that into a notification over the wire, then the server side generates a SIGWINCH on its side that propagates through its pty and onto the programs attached to it.

For an rs-232 attached classic terminal that can change rows/columns, all you've really got is running eval `resize` and updating the environment variables. Most visual programs will check the environment variables on suspend/resume and maybe (it's been a while) on full-repaint (e.g. ^L on vim).

As with everything tty related, there's a lot of history baked into the architecture. As new features arrive, you have to find some place in that architecture to insert it, perhaps awkwardly, but it beats rewriting the world.

So we start the interactive age with teletypes, keyboards and paper. Nothing beyond printing the characters, ringing the bell, and the basic ACSII chars for moving right (SPACE, TAB), left (BS, CR), and down (VT, FF, LF). The main editor is a line editor called ed.

Move ahead a few years and you have 'glass' ttys, every one of them different. This is the termcap and curses era. The screen size is baked into the termcap entry. Editors are now interactive 'screen' editors, vi and emacs mostly. Pretty soon, some terminals can support multiple font sizes and the LINES and COLUMNS environment variables can override the termcap entries. Terminals are still separate devices connected via RS-232 and all communication is in-band.

Move ahead a few more years and we're now in the era of workstations with bitmapped graphics (and their Mac and PC equivalents). 'Terminals' are now interactive graphics programs that run under the window system (either X11 or proprietary), so they need to translate kbd and mouse events into the ASCII byte stream onto a pty to emulate the old RS-232 convention to talk to the "line dscipline" part of the kernel's tty driver. But now, changing the size of a window is trivial; people do it all the time. They do it in the middle of vi sessions. They do it when they've ^Z'd out of vi and then expect vi to know the new size when they fg back into it. You can't just blast escape codes onto the line as whatever is reading stdin is likely not equipped to deal with it. At the very least, the in-band exchange has to be initiated by the 'computer' side of the pty. So, they added SIGWINCH and it was an out-of-band signal sent from the terminal emulator program through the pty (which, again, is a software abstraction in the os as opposed to an RS-232 line) to tell the other side of the pty that, when it has a chance, it should re-query the size of the terminal. It took a little while to nail down the semantics of the shell notifying backgrounded processes, but it got the job done. But it likely doesn't make a lick of sense to anyone that doesn't remember the good ol' days.

Will their existing suits work on SpaceX or will SpaceX-compatible suits need to be flown up? If the latter, I wonder what the odds are of a suit-related problem (e.g. doesn't fit, won't seal, etc).

A truly fitting punishment would be that Boeing is prohibited from piggybacking certification of any further 737 variants.

Yeah, my dad was my first bully too. First at my mom and then shifted towards me once I got old enough to have independent thoughts and interests (around 6-7). Led to me being a twitchy, withdrawn kid which garnered more negative attention at school.

Ken Shirriff, naturally, has tackled the subject a while back in a multipart analysis of the Yamaha DX7.

https://www.righto.com/search/label/dx7

Close, things like PCI and AGP (i.e. fast/wide parallel busses), not PCIe.

Everyone in the late-90's recognized that parallel was maxed out and GHz SerDes with embedded clock recovery, adaptive equalization, lane skew compensation, error detection, etc. was the future. Future I/O (IBM, HP, Compaq, 3Com, Cisco, ...) and NGIO (Sun, Dell, Intel, ...) were competing efforts that eventually merged and then rebranded by Intel as InfiniBand. But IB had the usual design-by-committee disease as it tried to shoehorn in networking, io, and system interconnect roles. Intel then bailed from the effort and serialized PCI instead. Intel tried to get back into that game in the 2010's with OmniPath without success.

Searle's finally going to get his Chinese room.

Wondering about pH and leaching mercury...

As someone who has had a couple bad back and neck injuries, the idea of being able to position hi-res displays anywhere in space is very attractive. $3500 would be totally worth it if I can tolerate it for the day.

Is this one of the models that had its radar removed or disabled? I'm not saying working radar would have prevented this accident, but working radar would have prevented this accident.

I wonder if there's any issue with disorienting pilots - having lights sliding along the ground could provide misleading visual cues. I know the flashing lights on tall objects are sync'd specifically to avoid any illusion of movement. Probably more of an issue in the US where there are a lot of low-currency private pilots flying night VFR.

"2010: The Year We Make Contact" is a much more accessible movie that holds up pretty well. It also feels like a payoff after investing so much time being confused/bored by 2001.

I was 11 when "Logan's Run" came out. Yes it's kinda loaded with 70's sex tropes for the first act, but it's also equal parts goofy and a really good film.

The original "The Day The Earth Stood Still" holds up.

"A Boy and His Dog" is a bit crude here and there, but might resonate with a 12yo.

"Quatermass and the Pit" (aka "Five Million Years to Earth") is both intense and fairly tame.

A lot of old TV series hold up - Twilight Zone, Outer Limits, UFO, Space 1999, Star Trek TOS, etc all have some excellent episodes.

I absolutely love "Dark City" and "12 Monkeys" but I'm not sure they'd have held my interest at 12.

Doctor Who, both old and new are excellent. Though I'm partial to the Tom Baker era.

The Stargate franchise is pretty good.

"Moon" (2009) is a bit cerebral but a good SF story.

stdint.h includes definitions for format strings for printf/scanf-type functions (e.g. PRId64, ...) for all the new types. Using them is a bit clunky (e.g. printf("%"PRId64"\n",n);), but you get used to it.

It was broken, then it worked, then it was broken, and now it works again.

Also, remember, if you got logged out, you've been bumped out of 'latest' mode if you were using it.

What you're describing as anhedonia also includes avolition. At least in my case, there are three components that feed back into each other: avolition - that lack of impulse to do ... anything, even when there are strong stimuli; executive dysfunction - even if you're ready to act, a sense of being overwhelmed by choices and unable to put one foot in front of another; and anhedonia - even if you're finally doing something pleasant or productive, there's absolutely no mental reward or lasting sense of accomplishment to build upon. A row-row-row-your-boat of suck as it were.

I wonder how having engineers running errands at the boss's side-hustle benefits TSLA shareholders.

I think he's the very model of a crank - he's been actively pushing a hypothesis mainly defined for what it isn't for at least 30 years that's been kicking around for over 60 years that's failed to make a single successful prediction and repeatedly gets falsified and instead cherrypicks new results and goes "See! Everything about that model is wrong and therefore mine must be right." The Big Bang just broke some people.