This was really frustrating me. YT started recommending this channel and I could recognize the voice as an AI impersonation but had no way to know if it was at least reading something really written by Feynman. Eventually I concluded it wasn't, but there wasn't clear criteria under which I could report the channel. I'm not sure it's even against YT's TOS.
I think you're not technically wrong, but you're defining NAT differently than the majority of people you're arguing with (those who assume NAT also implies a firewall blocking inbound connections), and the remaining minority (the "on the WAN subnet" crowd) are dismissing outright the idea as a reasonable attack vector that an attacker close enough to be able to send packets destined for non-internet routable addresses to your router.
Is the latter something that was/is actively exploited?
It's there in the name - "Rust graphics community" as opposed to simply "the graphics community". Language fetishization above the end goal - or, rather, the language fetish is the real goal.
If you want heavy concurrency, to get some value out of all those CPUs on a desktop, you need all the help you can get from the language. Unity and Unreal pushed it through in C++, but both required huge efforts.
If gRPC overhead is critical to your system, you've probably already lost the plot on performance in your overall architecture.
You make a fair point about smart pointers, and median "modern C++" practices with STL data structures are unimpressive performance-wise compared to tuned custom data structures, but I can't imagine that idiomatic Java with GC overhead on top is any better.
He definitely made games. Chris Crawford was one of the first known names in game design, a few years ahead of contemporaries like Sid Meier whom I expect you'd still recognize. Crawford seemed to alternate between computer war games, with reliable prospects for commercial success in the 80s, and more experimental fare about managing nuclear reactors, geopolitics, and such - difference being he seemed to get bored by the whole thing and completely disembarked in pursuit of whatever it was he intended to achieve via Erasmatron, Storytron, etc. It's fascinating to read his writings over that period. It seemed a sort of tragic paradox overshadowing all of it that, if he was so bored of mechanistic, algorithmic, and predictable computer game mechanics, maybe stop pursuing computer games as your chosen medium? It may have been a blind alley in the end, but someone had to explore it.
Nevertheless, it is quite sad - however, it's difficult for me to relate to the experiences of someone who lived through that first wave of personal computing and played a notable part in it - perhaps through that lens, anything was possible.
The 8x16 font from the Atari ST's hi-res mode is pretty slick if you like something bold and a little futuristic.
https://github.com/ntwk/atarist-font (or rip it directly from the ROM)
It is of some practical use, but there are a lot of slightly incompatible versions of the IBM PC and of MS-DOG, so it doesn't offer the kind of strong reproducibility that I'm looking for.
A DOS-executable is far more write-once-run-anywhere now than Java ever was, and the best thing is that no one is going to ever deprecate any API in DOS. There is no software rot in a dead OS.
There's still a few Common Lisp features the mainstream would benefit from ripping off. Relevant here is the condition system. Conditions and restarts are still foreign enough that it's hard to explain to people why the "debugger" was a fundamental part of the lisp machine UI, and how much sense that made, and harder still to fathom how you'd adapt that to Unix, where it would morph into some kind of weird IPC tied into the command shell.
It's not just about being able to stop your program and hot-patch code to recover from errors - this should be trivial in any dynamic language. Rather, it's about being able to composably control how to recover from exception conditions (or, really, any branching behavior) both interactively and programmatically in a unified framework.
