Dan Abramov

Dan, this has nothing to do with React or frameworks. What I'm trying to say is: just imagine if these weren't technical choices and we had to *invent* ways of styling, passing data & writing components. I don't know if people are trying too hard to misunderstand the tweet.

It has to do with React because you are prominent in the React community. Whether you want it or not, people from other communities reading this will think “React developers agree with this person that I’m insane for liking e.g. CSS”.

Sane might have been a wrong word. Maybe "experienced". Still, people are misunderstanding the "invent" part of the tweet. If we had to *invent* styling most experienced developers would choose tight coupling of styles to elements (otherwise Sass/Less/BEM/Modules wouldn't exist)

Again, you’re implying that the other side of the tradeoff only appeals to inexperienced people. This is super patronizing. Have you considered that maybe you lack the experience to appreciate simpler options that match the problem domain more closely?

By "experienced" I don't mean anything else but a person who has i.e figured out all the flaws of the Cascading Style Sheets and decided to adopt something like BEM, CSS Modules, or css-in-js. And that's 99% of frontend developers.

But what about the person who figured out all the flaws of css-in-js, and being familiar with flaws of both approaches, picks the one that better fits he problem?

First, if we would "invent" css-in-js it wouldn't be called css-in-js. Second, it wouldn't work like css-in-js does right now. Because we would *invent* a way of styling. The styles are gonna be coupled to elements. No cascade. I think most of the devs would choose that.

This is more nuanced and your original tweet failed to capture that. Although even cascade is useful for styling documents for multiple possible presentations. It would be useful to invent on top of those “new primitives” you’re imagining.

Thanks @dan_abramov for saying this.

This is not the first time. See other tweet how he trashed native devs when airbnb sunset RN. Unfortunately, @kentcdodds endorsed this guy.

Wait... What do I have to do with this?

Sorry I might be wrong. You used to tweet we should follow this guy. I am sorry if I am wrong. You are great :).

I probably did. Either way I still recommend following him. I don't endorse everything the people I follow say, but I do like to listen and understand. I'm with Dan on this specific tweet, but Kitz is an awesome person who puts out interesting stuff.

Kitze*

I agree, I think it’s our job as community to call each other out when we say something alienating and biased. I don’t like unfollow mobs.