Like, for your example, if somebody's writing a gen story for a canon that they feel is slashy, then they should just write it the way they see it on the screen and let the slashiness shine through to readers who are wont to see it.
Yeah. I always say it's easier to read slash into something than it is to read gen into something, so it's not like the subtext is really needed. Plus an argument I often make about gen vs slashy subtext-gen is that most gen readers are looking for stories that - if possible (depending on canon) - stay away from pairings, and that includes hinting at pairings. And slash readers aren't going to scour gen fic hoping to stumble on slashy subtext. So why not just make it slash or at the least label it pre-slash, let readers know what they're in for, and make both parties happy?
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2012-05-16 09:09 pm (UTC)From:Yeah. I always say it's easier to read slash into something than it is to read gen into something, so it's not like the subtext is really needed. Plus an argument I often make about gen vs slashy subtext-gen is that most gen readers are looking for stories that - if possible (depending on canon) - stay away from pairings, and that includes hinting at pairings. And slash readers aren't going to scour gen fic hoping to stumble on slashy subtext. So why not just make it slash or at the least label it pre-slash, let readers know what they're in for, and make both parties happy?