I am of course talking about Emily Short. In the year 2000 or thereabouts, she made a short interactive fiction story called "Galatea." ( https://en.wikipedia.org/wiki/Galatea_%28video_game%29 ) I highly suggest trying it out.
I think it's sad how fourteen years later, similar to the devolution of FPS's from Quake to Call of Duty, some new text adventures may have gained a much wider audience and are praised to high heaven but are clearly inferior artistically and in design.
FPS games used to have very simple orthogonal game mechanics. Large amounts of complexity would arise from those small lists of simple game mechanics. A 'board game equivalent' to this concept might be Go (or if we are being less flattering to the video game industry, Draughts/Checkers). This orthogonality was best showcased in weapon design; you'd often have less than 10 guns, which each behaved in completely different ways and were best used in completely different situations.
Q3A examples:
gauntlet: the only melee weapon
machine gun: hitscan, accurate, fast rate of fire, low damage.
typically available on spawn.
shotgun: hitscan, inaccurate, slow rate of fire, large damage when close.
must be picked up.
railgun: hitscan, accurate, slow rate of fire, devastating damage.
must be picked up.
lightning gun: not-quite-hitscan beam, medium-short range, high damage.
must be picked up.
etc...
Modern games, typically aiming for some perverse sense of "realism", typically lack this sort of weapon orthogonality. You get typically get the basic categories of "assault rifle", "sniper rifle", "handgun", "submachine gun", and "something that shoots explosives", which is all fine and good, except each of those categories has half a dozen or more variations that have very boring differences. Like 6 pistols that only differ in clip size or damage (with one or two clearly being the dominant weapons in all situations). For a concrete example of a game that I think suffers from this: Watch_Dogs. 10 different handguns, but the only one that it ever makes sense to use is the handgun that you start the game with (accurate, silenced, and semi-automatic. yeah there are the automatic handguns, but why would you use them when you could just use one of the automatic rifles? The game gives you absolutely no reason to care about the other handguns).That's just weapons. I have observed similar trends across nearly all other game mechanics in modern shooters. It is like game developers forgot how to create complexity from a small list of simple mechanics and instead just pack games full of shallow features.
When you play or watch a game, try the following: Imagine that all the models and textures were swapped out with generic low-poly abstract placeholders. All handguns are small thin blue boxes, rifles are all long thin teal boxes, etc. Does the game still play well? If it is Quake or Doom, then the game plays exactly the same as it did before. If it is a modern game, then chances are several pointless redundancies become obvious and several previously "neat" game mechanics become obviously shallow. They have several "different" game mechanics that are different from each other only in the model, texture, or animation used.
Mario-Party-esque "Push X to perform [every damn action in the game]" stuff is another biggie for me. Incredibly lazy stuff which apparently appeals to modern gamers.
The what now?
I agree. Can you imagine anyone daring to post a negative opinion about this article? They'd be verbally assaulted, down voted and shadow-banned in minutes.
Did any of them say "This article will only be about men"? No. I'm not clear of your point -- do you wish all articles which only discuss men were labelled as such?
"Sexist" is a normative term. It describes an "ought". Specifically: sexism points out instances where we "ought not" stereotype genders. So it would be sexist to point out that women as a class are inferior or superior at video game development. This post does neither of these things.
The term you're flailing around for is "gender biased". "Gender bias" is a descriptive term. It describes an "is". This post "is" about highlighting the achievements of women in the industry. It uses gender as a criteria for inclusion.
By itself, gender bias leaves you with too many unknowns to solve the system for a normative result. You can add intent and circumstances (for instance) to solve it for impact. If you think the intent of this article is to suggest that women are superior to men, you'll sound like a crazy person. If you suggest that the circumstances of gender balance in our industry are such that women's achievements are nonnotable, you'll sound like your head is in the sand. But you haven't even done either of those two things; you've got x, y, and z, one equation, and have just decided to leave y and z out and declare the system solved.
I haven't figured out a good example of something that is sexist that doesn't display gender bias though...
I agree. However, this isn't a Wikipedia article (which should usually be accompanied by a similar article about the opposite sex). And this article has some issues (IMO) that a Wikipedia article wouldn't have; I won't list them, as I said in my first comment, but @pervycreeper list some of the issues he sees.
> The term you're flailing around for is "gender biased".
Possibly. However, in my mind "sexism" (along with every other "-ism") is defined as any (irrelevant) discrimination, including positive discrimination. Therefore, I perceive the current "more women in CS" craze (nor the general "more people in CS" trend) as inappropriate/(unfairly) biased/-ism. Of course, we might argue whether it's irrelevant or not; personally, I was brought up in a different society where everyone had to work, my mother was the technical person in the family, and if anything, I was discouraged from spending too much time behind the computer, so I'm convinced that in my country, in my generation, computer skills are the result of means (computers were much more expensive back then) and interest, and not gender at all; if I were brought up in the US, I might have a different view on sexism in CS.
The reality is: people who talk about "reverse sexism" like this are, almost as a rule, trying to minimize discussion of sexism against women. I'm now discriminating against you based on that statement, but it's OK, because that discrimination isn't irrelevant: there's a search bar at the bottom of the page, and it's really easy to use it to see where you stand on this issue.
Possibly. But as they say, "be the change you want to see in the world".
> people who talk about "reverse sexism" like this are, almost as a rule, trying to minimize discussion of sexism against women
Well, there is sexism and there is "sexism". If we're talking about things like forced marriage (more specifically, older men marrying underage women), FGM, human trafficking/sex tourism, violent rape, etc., I'm all for it. Of course, these topics are rarely discussed, because there is no discussion necessary - pretty much all people agree that they are awful, and that they should be solved.
On the other hand, if we're talking about things like GitHub's meritocracy rug, "the patriarchy", that the female CEOs are paid less than male CEOs, that there should be more women/people in CS, or domestic violence against women, then I'll be pointing out a few things; (1) these topics are not really deserving of the attention they're getting (poor millionaire CEOs; why don't we talk about the homeless people instead), (2) they are sexist (why not talk about domestic violence in general - recent studies suggest that there is a huge number of male victims as well, and no support systems for them), (3) they often have a hidden agenda (noone wanted to be a programmer before geeks became cool and started earning a lot of money). IMO, these are all very valid arguments, but because they are comments about sensitive topics, they get downvoted.
If you haven't already done so, I suggest you read "What You Can't Say" by pg (http://www.paulgraham.com/say.html) and Letters to a Young Contrarian by Christopher Hitchens.
I think so to. However, others disagree; you can check my comment history.
I've read pg's essay. Thanks for the other recommendation.