It doesn't sound like gatekeeping to me.
Gatekeeping is trying to prevent someone from doing something. This sounds more like a lot of people just saying that it sounds like a nightmare for reasons non-devs might have trouble understanding and they wouldn't want to touch it.
So it's going to get bought out by Microsoft and replaced with a shitty electron app?
Holy shit I think with the joke, irony, and the two of you, I might be able to put some sort of perpetual motion machine together! Now I just need some investors...
Yeah, if someone can't help but destroy objects around them or punch holes in walls, I wonder how many bad days or situation escalations they are from targeting a person instead of an object. Rage isn't a pressure vessel that needs pressure to be released in the form of violence, rather your mind is something you train habits into, meaning you're training yourself to react to frustration with violence.
Not to mention it never helps anything. You mentioned the feelings of shame, but there's also more direct consequences of destroying things that happen to be in reach. There was a bash quote from someone who had to print a school paper or something and got so frustrated when they couldn't access the file that they threw their printer (or something essential to what they needed to do) out of their high storey window in frustration. They were lucky they didn't accidentally kill someone in the process, and then had a new real problem of not having equipment they needed once they realized the disc or whatever the file was on was sitting on their desk instead of inserted for reading. Or videos of kids getting gamer rage and destroying their keyboards or monitors. That will just make it harder to stop being pissed off because now they need to spend money to get back to where they just were (and were already unhappy about).
Though I do feel differently about object destruction not done in the heat of the moment. Like the printer scene from Office Space or getting enjoyment from demolishing a room before renovating it. It's a deliberate choice, which doesn't imply they might fly off the handle and do who knows what.
Fun fact: the first capitalist ventures were colonial missions (Spanish missions to the Americas). The first publicly traded corporation was the Dutch East Indian company.
Though I'd say the root of all evil is imperialism or the desire of some to spread and maximize their control and wealth.
Technical analysis is where gambler's fallacy meets self-fulfilling prophecy. Though other forces are also in play.
Personally, I think the problem was that they were being bullied, not what specific names they were being called.
Not hating on VR but it's still a far cry from a holodeck.
Though ironically, this will make it easier for Chinese to blackmail those who get lonely and have relations anyways, since the relations themselves could be used to threaten jobs, rather than needing some extra step to make it scandalous.
I mean, that image is pretty rude, too.
What's stored is hash(password). Then the password check is stored == hash(entered).
Hash(x) will be the same length, regardless of what x is. What that length is depends on which hash function it is. So the database can set the length of its storage for each user's password to the length of the hash and the hash function will take any size password.
The language actually only consists of a relatively small number of verbs. Operations that perform various mathematical and logical actions (such as adding, multiplying, dividing, and, or, xor, bit operations, and comparisons), assignments/reads (put the result of this string of operations in this container for future use or read one back to use it now), conditionals (check if this condition is true, if it is do something), and jumps (instead of going to the next instruction, go somewhere else).
Everything else is just variations or combinations of those four basic things. Don't worry if you don't know what anything is in the following paragraph, it's just explaining how everything else is built on those basic pieces.
Loops are all four put together, functions are assignments and jumps, objects are a way to organize functions and data, polymorphism is a modification that allows replacing function code in variations of the objects. Even IO is just assignments and reads to and from specific memory addresses. Programming language primitives and APIs will simplify doing these (you aren't likely to do IO as those memory mapped operations directly unless you're working on drivers or embedded apps). Sometimes the CPU itself implements special cases, like atomic operations or having multiple cores so you can have multiple threads of execution running in parallel.
When I realized this, it made learning new programming languages much easier. And the internet puts all of the more specific information at your fingertips, especially when you consider all of the free university courses available that go into specializations of the above, plus the other important meta aspect of programming: algorithms.
I suggest you pick a language and just try diving in. The early exercises will seem overly simple, but they'll build a foundation that you can then build more on. For easy to pick up languages, try BASIC, python or lua. Scratch might also help, though it's purely gui based, so might be harder to jump to another language from there (which you'll likely want to do to develop an app).