I'll freely admit that I was too much of a newbie to really appreciate Multics during the precious year or two I had access to it, but the single abstraction for memory and files seemed like a great approach...
This has been going so well for such a long time. It will be absolutely heartbreaking if the probe is incapacitated just during the flyby window.
Most articles I've read about this point out that the risk to any given swimmer is still extremely low. We all know that humans are bad at weighting risks from very low-probability but high-horror events.
By the same token, though, the risk to any given golfer out on a course during a thunderstorm is pretty low -- but nearly everybody agrees that going out on a large, open expanse and holding a metal stick over your head during a thunderstorm is kind of stupid.
I can't say that I blame people for deciding to stay out of the water.
I started out with a TRS-80 Model I in high school. I spent a lot of time on that machine, and applied a lot of the "canned hacks" developed by others -- add-on hardware better than that Radio Shack sold, a memory remapper to let it run CP/M, soldering in another 1024x1 RAM chip to support lowercase video, jumpering the clock divider chain to effectively overclock the CPU, and so on.
Eventually, I noticed that I was starting to have wrist problems, especially when I used WordStar -- that WP used the non-existent Control key quite a lot, and the CP/M port mapped it to one of the arrow keys, which was an ergonomic nightmare. But I happened to find a pair of foot switches on clearance at Radio Shack, pre-wired to mini audio plugs. I drilled two holes in my system unit, mounted two mini jacks, and wired them to the keyboard in the same position as the shift key and that arrow key. Stomp-K-D for the win! My wrists were better in no time.
Later, I got a state-of-the-art 1200bps modem, but my poor terminal program couldn't keep up. Any time the screen had to scroll, I dropped characters. The solution: I rewired the 40Hz real-time interrupt to fire at 160Hz, and wrote a little interrupt-driven driver to catch and buffer characters coming in over the RS232 interface. It was completely bulletproof. Unfortunately, it also sped up the keyboard timing (repeat delay and rate) by 4x in CP/M.
I guess the biggest hack, though, was building a full character-based video display subsystem that hung off the expansion port. Forty or fifty SS/MS LSTTL packages spread across eight or ten solderless breadboards, with a couple of static RAM chips thrown in for character generation and storage. It ended up being something like 30 lines of 100 characters, comfortably larger than the original 16x64 display or even the 24x80 displays in the computer labs, and each cell was 8x16 pixels, so they were nicely readable characters. Luxury. I used that "in production" for a year or two, until I managed to land a Lisa.
...reading your op-ed (as opposed to, oh, I don't know, an actual report containing actual facts).
One of the unique characteristics of the Internet is that it provides a way to monetize tiny minority tastes. That way, bozos can produce books or videos on "Down is Up", "Beanie Babies: The New Future-Proof Investment", or "The Unexpected Triumph of Old Media in the Digital Age", and find enough paying customers to make it worth their while.
Golly! How do you suppose that having one person at a time writing code, with the rest of the team effectively doing simultaneous code review, magically produces "fewer features" but "better code quality" than having everybody writing code, then throwing it together and maybe doing a cursory bit of code review at the end?
Next, you'll be telling me that having one or two testers per developer produces better-quality software than spending all your money on developers so you can "get more features".
Turning the shield (conductive layer around the craft) into an antenna? I like this idea. And with the full paper freely available through the link in the source article, I could in principle learn more -- if only my math and EM physics were up to it. Sigh.
I've been waiting and hoping for that little probe to wake up and start chatting again. I know it's only a lump of machinery, but developing emotional responses to lumps of machinery is built into humans at a pretty low level.
...DO NOT welcome our new, tentacular, inner-body-exploring robotic overlords. Ick.
But if they turn out to be the effective solution for a life-threatening health condition, I'll find a way to cope.
Some of us are heteroromantic, biromantic, homoromantic, panromantic, demiromantic, or even aromantic.
We realize that different cultures have different hygiene practices, but really, can't you put on a bit of deodorant in the morning?
Oh, wait. Never mind.
"I was just being honest about my own shortcomings -- by talking about what 'you' do when there are women in the lab. 'You', of course, being a straight male, because duh, who else would I be bothering to talk to about science?"
Because I'm a victim
...from a solenoid big enough to simulate getting slammed in the head by a 350-pound goon?
Almost as repugnant as, say, gymnastics. Or ballet. Or any other "sport" or "performance" where participants are inducted at a young age, then subjected to agonizing and (often) permanently crippling stresses.
And these are security experts?