There's a book called Catch 22. Looks like the made a movie of it. The book is the funniest thing I've ever read. Made me think about how crazy fighting is. Sort of like a funny Slaughterhouse-Five.
Neither mentioned illegal orders as far as I remember. Was the movie quite different?
I think time wasn't super kind to it. And I don't remember how clear it was in the movie that Scott's just not a good dude. My memory of the story is that the core is: Scott is bad. Scott accepts that. Scott starts doing better. But maybe that's just my headcannon.
It's a good lesson though! Just because you were bad doesn't mean you are bad. You can change. Life isn't a simplistic video game. It's a lesson I've needed from time to time.
This image from the Wikipedia page is great.
Certainly hypole comparing it to the Hamadian massacres. Still. Good image.
It's weird I said "men" here. In the US women usually change their names once and men never. But adoption and grandma and going by initials are all changes I've seen and understand.
The story reads as totally normal. Not many men change their name that much but, "I want the same last name as my grandma who I love very much and not my second dad who I don't talk to" feels right and good and maybe even sweet. The man's a monster. This is fine.
Would we remember Batman the Animated a series without Kevin Conroy and Mark Hamill? Maybe.
I worry it would have fallen off. Now we can always dream of what could have been.
I've always wondered about Unicode normalization and passwords. I don't know a ton about it, but I think it's that things like ö and be represented as one character for the whole thing or two, one for the umlaut and another for o. That means that there are at least two sequences of code points that make the same... Glyph? I forget the word. The thing you see on the screen.
Anyway, what if you have that ö in your password and one browser/keyboard/os/lovecraftian nightmare makes the mark one way and the other does it the other way? They aren't the same bytes. So they won't hash the same and you just can't tell why. Without digging super deep.
There are standard ways to normalize the Unicode but I don't imagine most password systems use them. Maybe it's some intermediate layer. But I kind of doubt it. Those are complex, evolving standards.
Oh. And that "evolving" thing might make trouble for password systems. Are these standards backwards compatible in the way they'd need to be for a normalization upgrade not to break any passwords?
Oh God, what nightmare have I found?
I was in Vegas a couple weeks back. Same problem.
We're two years out from the API apocalypse. I think. That's how I got here.