They are not bad at this. You are bad at understanding it.
I work with this stuff, and I do understand it. Some of my colleagues are actively participating in USB-IF workgroups, although not the ones responsible for naming end user facing things. They come to me for advice when those other workgroups changed some names retroactively again and we need to make sure we are still backwards compatible with things that rely on those names and that we are not confusing our customers more than necessary.
That is why I am very confident in claiming those naming schemes are bad.
"don’t even bother learning it" is my advice for normal end users, and I do stand by it.
But the names are not hard if you bother to learn them.
Never said it is hard.
It is more complex than it needs to be.
It is internally inconsistent.
Names get changed retroactively with new spec releases.
None of that is hard to learn, just not worth the effort.
Sorry, didn't want this to look like an attack or disagreement. Just wanted to highlight that point, because arbitrary maximum sizes for passwords are a pet peeve of mine.
At least the character limit had a technical reason behind it: having a set size for fields means your database can be more efficient.
If that is the actual technical reason behind it, that is a huge red flag. When you hash a password, the hash is a fixed size. The size of the original password does not matter, because it should not be stored anyway.
Any sane parent would worry about their kid getting killed a lot more than about them suddenly transitioning to another gender even if both of those were real things that actually happen.
TL;DR: The USB Implementers Forum is ridiculously bad at naming, symbols and communication in general. (And they don't seriously enforce any of this anyway, so don't even bother learning it.)
At some point accumulating more money is no longer about added utility and more like a kind of cynical game score. And musky boy is clearly chasing that high score.
So his "crime" that you want to punish him for is that he improved things in a way that made sense in the context of his time instead of looking decades into the future and forcing a drastic change immediately long before society was anywhere near ready for it? Seriously?
While I do agree with your general sentiment, please consider not using "retarded" as a derogatory term. It is hurtful for people with intellectual disabilities and effectively acting as a slur against a minority group.
You can buy gold (and other precious metals) as exchange traded commodities, no reason to have them physically delivered to your home and risk damaging your floor.
Biden should give an executive order to lock this guy up for treason.
When people complain about that, point to the SCOTUS decision that the president can do whatever the fuck he wants without legal repercussions.
If any of the people who complain even vaguely hint at violence in reaction to this, give an order to lock them up for treason, too.
Keep this cycle going until the last grunt has understood that this type of behavior will not stand.
Once all the people willing to call for violence are locked up, use the same reasoning to disband the current SCOTUS and replace it with something that is not an embarrassment for a modern democracy, with a strong recommendation to immediately renounce the ruling that made all of that legal.
By the time the dust has settled Biden will be too old to be persecuted for any of that anyway.
I know none of this will happen, writing it out just as a happy little fantasy.
The Next Great Thing(tm) will not make a number of users that is significant to any real world scenario move away from Windows. The only approach that might have a chance to do that is something that looks and feels as close as possible to Windows. Yes even the parts of Windows that are bad. All of it, except the most glaringly obviously horrible stuff (like ads in menus). And that also includes all the programs a significant number of users care about either running there out of the box without having to jump through any hoops or a replacement fulfilling the same "looks, feels and operates almost identical" criteria.
People care about something feeling familiar and not having to relearn stuff a lot more than about shiny new features.
I work with this stuff, and I do understand it. Some of my colleagues are actively participating in USB-IF workgroups, although not the ones responsible for naming end user facing things. They come to me for advice when those other workgroups changed some names retroactively again and we need to make sure we are still backwards compatible with things that rely on those names and that we are not confusing our customers more than necessary.
That is why I am very confident in claiming those naming schemes are bad.
"don’t even bother learning it" is my advice for normal end users, and I do stand by it.
Never said it is hard.
It is more complex than it needs to be.
It is internally inconsistent.
Names get changed retroactively with new spec releases.
None of that is hard to learn, just not worth the effort.