@jalcine @braindouche I'm happy to be wrong & reframe my analysis around any theory that makes more sense of the senseless waste I've observed. Maybe @braindouche is on the right track! Will think more on this.

Appreciate thoughtful engagement.

@slightlyoff @jalcine @braindouche

Continue to feel a lot of this was due to (mostly men) who wanted to distance themselves from the girly stench of HTML and CSS via "real" programming.

I suppose they at least succeeded in inflating FE salaries as a result. Arguably a win.

The bizarre 2-4 year period where that crowd absolutely obsessed over purity and monads in their JS code only underlines my thinks there... FP is as "hardcore" as it gets to a certain personality type.

@betsythemuffin
To an extent, yes absolutely, but also I personally think that prejudice is secondary to the sheer scale of the recruitment problem that web 2.0 presented. That recruitment problem was solved, by and large, by making front end development work a lot more like back end development, specifically java. Which is a wildly simplified way to describe it, but that's what happened.
@slightlyoff @jalcine

@braindouche @slightlyoff @jalcine

Hmm. I don't actually think prejudice qua prejudice was a significant factor in the re-gendering of frontend.

I think the gendering of frontend as femme enabled the fundamental *contempt* for HTML/CSS best practices that underlay and powered the frameworkification of frontend.

@betsythemuffin @braindouche @slightlyoff @jalcine and I think that (gendered) contempt for simple HTML/CSS is load-bearing in understanding just how/why folks were so willing to accept *complete bullshit* from framework promoters.