The important part of understanding the context of this discussion is that the CSS community was very unwelcome to any new CSS tools. As a creator of PostCSS, I understand Adam’s reaction.
For me, it is not only about “constructive criticism” vs. “author’s feelings” but also about the hostile environment created by the CSS community for CSS tools authors, which blocks a good discussion and tools evolution.
Yeap, the CSS community unwelcoming was not in that specific conversation of Adam and Sara. Sara (in contrast to many CSS guru) talk about CSS toolings in public.
As usual, it is a case, when we have many US white developers creating unwelcome environment, which then leads to these conflicts.
It seems you are calling Sara's behavior here toxic. She wrote a lengthy tweet that disclaimed the article made some good points, but that she didn't agree with all of it, nor the tone.
Are you suggesting that you believe her sharing the article, along with her framing, is somehow a justifiable catalyst for Adam's passive-aggressive, manipulative public shaming of her?
I didn’t. I am calling CSS community in general toxic to CSS authors. Many popular people in CSS community are hostile to CSS tooling and use their public channels to prevent CSS toolings from having discussion platforms. It leads to more conflicts and lack of good discussion about CSS tooling limits.
I mantioned that Sara is better than rest of community.
Sorry, English is not my native language. I am guest on your territory.
Apologies, I just wanted to clarify. There's no need to apologize for the language barrier. I'm happy to take the extra time to ensure we are understanding each other.
I agree that many people in the development community, not just CSS, are toxic to each other, not just the authors of tools. It's also to folks like Sara who simply make educational content. And in many cases, the authors and communities around those tools are also aggressively toxic to outsiders.
Even Adam's own marketing is quite flagrant to the CSS community who create and educate "best practice" paradigms like BEM.
It is a terrible framing to begin with to critique and work to make better tools, I absolutely agree.
I see a big difference in community and tools communications in CSS and rest of the fields.
JS’s TC39 invited Babel author to speak abut polyfills lmits on their meeting, but CSSWG is trying to avoid CSS polyfil community.
I know a few cases, when popular people (no Sara) keeps their article outdated to hide new CSS tooling features from the community. Which is insane for JS community.
I can’t remember whem podcasts invisted CSS tooling authors.
Big important releases and initiatives were motly ignored by CSS opinion leaders (for instance, when Autoprefixer/Browserslist started to fight for brower diversity against US’s trends to ignore Chinese browers on gobal websites).
I beleave that it is a part of conflict between JS and CS community. But CSS tooling is not part of JS world to be treated with this hostile. We try to give a more power to CSS community to help them in this conflict.
And of course, it doesn’t excuse toxic behaviour. But this conflict is a good reason to highlight this unique conflict beween the community and CSS tooling.
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The important part of understanding the context of this discussion is that the CSS community was very unwelcome to any new CSS tools. As a creator of PostCSS, I understand Adam’s reaction.
For me, it is not only about “constructive criticism” vs. “author’s feelings” but also about the hostile environment created by the CSS community for CSS tools authors, which blocks a good discussion and tools evolution.
Given that Sara didn't write the criticism, and Adam said that the criticism didn't bother him - your reply here is odd.
No one should be understanding of passive-aggression and manipulative guilting in front of a large, cult-like audience. It's toxic.
Yeap, the CSS community unwelcoming was not in that specific conversation of Adam and Sara. Sara (in contrast to many CSS guru) talk about CSS toolings in public.
As usual, it is a case, when we have many US white developers creating unwelcome environment, which then leads to these conflicts.
One toxic behaviour creates another.
It seems you are calling Sara's behavior here toxic. She wrote a lengthy tweet that disclaimed the article made some good points, but that she didn't agree with all of it, nor the tone.
Are you suggesting that you believe her sharing the article, along with her framing, is somehow a justifiable catalyst for Adam's passive-aggressive, manipulative public shaming of her?
I didn’t. I am calling CSS community in general toxic to CSS authors. Many popular people in CSS community are hostile to CSS tooling and use their public channels to prevent CSS toolings from having discussion platforms. It leads to more conflicts and lack of good discussion about CSS tooling limits.
I mantioned that Sara is better than rest of community.
Sorry, English is not my native language. I am guest on your territory.
Apologies, I just wanted to clarify. There's no need to apologize for the language barrier. I'm happy to take the extra time to ensure we are understanding each other.
I agree that many people in the development community, not just CSS, are toxic to each other, not just the authors of tools. It's also to folks like Sara who simply make educational content. And in many cases, the authors and communities around those tools are also aggressively toxic to outsiders.
Even Adam's own marketing is quite flagrant to the CSS community who create and educate "best practice" paradigms like BEM.
It is a terrible framing to begin with to critique and work to make better tools, I absolutely agree.
I see a big difference in community and tools communications in CSS and rest of the fields.
I beleave that it is a part of conflict between JS and CS community. But CSS tooling is not part of JS world to be treated with this hostile. We try to give a more power to CSS community to help them in this conflict.
And of course, it doesn’t excuse toxic behaviour. But this conflict is a good reason to highlight this unique conflict beween the community and CSS tooling.