This article provides the perfect view into React brain worms:

[oschonrock@mastodon.social]

@benschwarz

1000x this^^^^

I stopped doing front ends when this madness became pervasive and expected.

Give me a call when it stops.

[brunoph@breakpoint.cafe]

@benschwarz because product designers are allergic to native UI elements

[jaredwhite@indieweb.social]

@benschwarz @sir_pepe 🫠

[mattdarveniza@mastodon.social]

@benschwarz @sir_pepe this is not only React brainworms but is a double whammy along with "CSS isn't a real programming language so I'm going to ignore it and assume building something from scratch is easier than restyling".

[benschwarz@front-end.social]

@mattdarveniza @sir_pepe ignorance 101

[jeffehobbs@mastodon.social]

@benschwarz there's not a single web technology that I have more genuine anger for than React.

[ianrogers@mstdn.social]

@benschwarz Reminds me of the developer I once worked with that used JQuery to round the corners on divs instead of CSS

[advaith@mastodon.social]

@benschwarz I don't think this has anything to do with react necessarily, it's because the native elements don't provide a lot of flexibility. appearance: none didn't even exist until a few years ago. when the native elements don't meet the needs, the only option is to use custom elements

[alda@topspicy.social]

@mattdarveniza @benschwarz @sir_pepe which in turn generates CSS code.

[splendorr@mastodon.social]

@benschwarz I agree! I’ve been thinking too often, “There is so much unnecessary javascript just to cover up that no one wants to learn css”

and so much extra styling shipped, just to keep from having to write a few styles that apply to more than one element for fear of unintended cascade

it’s so exhausting. I used to ship tiny sites with great styling. now I work for a corporation where I get chastised for ever writing my own styles (while the provided components never look right)