,
10 tweets,
1 min read
Read on Twitter
I want "simple mfing websites" back too, but the way to get them back is web standards evangelism, not javascript-bashing.
best way to kill webpack is to promote HTTP/2 + <script type="module"> ... & seeing that comes from knowing the problem webpack solves
best way to reduce reflexive SPA writing is evangelizing history API + service workers. best way to kill React is web components. etc.
most bad JS is rooted in folks who are too contemptuous of front-end to work at learning standards-based approaches.
most JS-bashing is rooted in contempt for the front-end too. contempt culture gets front-end developers coming and going.
it's almost like contempt culture swims around front-end b/c front-end is "arty" and "for girls" and "not real programming" or something.
I like "simple mfing websites" because simple mfing websites are accessible to everyone. That was my way into a women-hostile industry.
"modern JS" exists in opposition to "simple mfing websites" in part to make front-end "realer programming" and raise frontend salaries.
Unless & until you understand both the technical AND the social problems "modern JS" attacks, & the ones it creates, you can't dismantle it.
the social problems propping bad JS up are industry sexism and the abandonment of web standards. quit yelling at clouds & start digging.
