This is no different than what happens when you give Google a very NSFW search but it doesn't contain any keywords that turn on the NSFW results. And while it's easy enough to work around with search, translate is another matter. What is the translation of the dirty word for penis? Google knows it--it can translate it to English. But the two standard terms have other meanings and I have figured out a way around that.
They kept jacking up the price but were many years behind on 64-bit. That said to me they were looking to extract cash, not support developers. And C# was just about as good but properly supported. And in time Microsoft closed most of the gaps.
I don't really think you need to understand the whole stack. Rather, you need to understand at least one level deeper than whatever you are using.
Back in the days of Turbo Pascal you had to know what you were looking at when the memory modified breakpoint went off and you got dumped to the assembly level. And you really had to understand it to deal with the 200mhz bug (there weren't convenient solutions at hand when I first hit it) or when I ended up making extensive modifications to the real mode support in the DPMI mode--never saw that mentioned anywhere. It was nasty--the library was fundamentally flawed and clearly had never actually been used as it declared real mode pointers as "pointer"--which had a very high chance of causing a segment error when the compiler emitted code that copied them by loading them into a segment:offset then storing them. And the debugger was flawed: in single step mode it was emulating, not executing. And the emulation would correctly "execute" an invalid segment register load.
Now, though, in C# I have yet to have any reason to look at assembly.
Sure, luckily nobody needs to understand the whole stack. I feel I do but that's just a mix of age + unusually varied projects, not necessity.
Have to admit I don't recall a 200Mhz bug, and all modern search results are about GPUs. As for DPMI, well back then I was just a kid and 640kb was enough for any kid ;) Then Windows came along and solved all that. I definitely knew what it was though because all the games used dos4gw...
The problem is they keep changing identity. From what they said Google is taking them down--it's just they keep coming back under new names. Killing a hydra is hard!
My experience is our local bugs go bonkers for LED headlamps (as in a lamp you wear, not a car.) There's nothing around here that normally likes to chomp on humans, but hiking by headlamp they get irritating by dashing just in front of your eyes all the time.
I suspect this is a big driver of the switch. Parents that do not want to give their boys a name that will cause issues later on.
Back in school it wasn't a problem, people knew "Loren" was male, "Lauren" was female. Now, an awful lot of people don't. It's an uncommon enough name that even if you were around back when that's how it worked you very well might not have known it.
As an adult I routinely get misgendered, but it's a so-what to me.
As a non-native English speaker I've learned never to gender English speakers from their names. I mean in emails and so on, when I haven't had a chance to meet them. No "Ask Ashley if she would like to join us...". "Would Ashley like to join us?" is the safe option.
Loren adjacent. In high school my girlfriend was Lauren and mine is Lorin. Friends over pronounced our names to differentiate. It doesn’t bother me to get misgendered, either. It never lasts past hearing my voice or seeing me, though.
On the phone I'm routinely thought female even when they don't know my name. I'm not sure what's up, to me my voice on the phone sounds very different than in person but it doesn't seem female.
reply