I’m not claiming form is feminine. I’m claiming some _other_ people consider skills in HTML and CSS as low value and, if they’re misogynists, therefore feminine. This was clear to most everyone else who read the article.
Opinions don’t need to be respected at all. Opinions, like beliefs, can be poorly thought out and need challenging. If you disagree, fine, but I don’t have to respect opinions I see no merit in.
That’s just how codebases evolve sometimes. It’s how XML became Xcode, for example.
> Try not to make assumptions about what I have investigated, who I have asked, worked with, or what my opinion is on the matter.
Try not to claim my experiences are invalid or disingenuous just because you haven’t had the same ones. I can only speak from my experience; there is nothing so binary as objective true or false here, if that’s what you are looking for.
It’s a bit of a cheap shot to characterize something as ‘argument from tradition’ when the clear purpose of the article is to criticize recent developments. I am not concerned with the conflation of JS and CSS simply, and solely, because it is a new development. I consider it a problematic new development.