The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
"... but that doesn't really jibe with microsoft's naming conventions either."
That is of zero concern for me. I couldn't care less what their conventions are. Mostly because I detest what they have done with the Win32 SDK names of structures and members. I'll use what ever convention(s) I feel like using. Here's one example : they continue to use this long pointer prefixing "LP..." on things. We haven't had to deal with long pointers since the 32-bit SDK came into being. The whole large-model programming thing was horrendous and I resent being reminded of it. For this reason, I never, ever use a LP prefix for anything. For the items I access that have to use it I always make a typedef to avoid it.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
I can totally understand that. I'm a little more forgiving I guess. Or I just see different naming patterns to be appropriate in different contexts - I switch up myself. In fact, in C++ I have a few different naming and coding styles and conventions I use depending on the particular "realm" I'm coding in. Different languages, different conventions, too.
But that's me. To each their own.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
Some time ago I reported that, when debugging C++ in VS2017, you can't always see what a unique_ptr is managing[^]. The same thing sometimes happens with other containers, such as <list> or <set>. That is, you can inspect the container's private members, but not the items that it actually holds.
I'm starting to think there's something wrong with my system, given that this problem report has attracted no interest. But if you've experienced it, please upvote the item so that they will fix it instead of triaging it.
That surprises me, I had a Logi K/B for five or so years without problems - it replaced a fifteen+ year old "really cheap" k/b I bought with my first "real" PC (i.e. with a 486 processor). And I only replaced that because Herself complained I'd worn the legend off nearly all the keytops and she couldn't work out what letter was where ...
Currently using a MS 600, and it's not too bad at all: good travel and the feel is ok, if a little noisy. "A" and "S" are unreadable already though, and it's only a few years old (maybe four?)
I have the same experience a Griff.
So I counted backwards and realized that my logitech Internet keyboard 350 is eight years old.
Pity the letters are printed on the keys, because my s and a aren't that readable either.