[kowdermeister]

There is no "fix" to this. This is how people work. Some like things some don't, you have to deal with it or look for a more secluded hobby. If you can call it a hobby. Maybe behind every angry post there is a frustrated developer who've thought or been told that XY framework "is-the-shit" and and it will rock the way he works. Then he tries it and faces a series of problems. One consequence might be that he feels stupid, inadequate or incompetent. But there are some who dare to criticize. I thing that's a good thing. The moment when your mainstream project stops receiving criticism is probably the day it's dead. And by criticism I don't mean personal attacks (screw those idiots). By criticism I mean people with constructive feedback. The "angular 2 is terrible" article had plenty of it, besides the title it was a good read and insight how A2 really works.

If you want to reduce developer frustration, then try these things first:

- Write a clear scope what your project is about and how you intend it to used. Many times devs realize that the tool is a bad fit for them only after attempting to use it many times

- Write exceptional, up to date documentation

- Visually display core architecture explanations

- Provide clear getting started examples that work out of the box

- Communicate well breaking changes, updates, milestones

[magicalist]

Why would a project maintainer be expected to write "exceptional" documentation, have a clear scope for something they might still be exploring, give visual architecture explanations, etc etc and we can't expect developers to deal with frustration like an actual human?

[kowdermeister]

These project aim at the bleeding edge so if a maintainer sets the bar high, then it's expected to keep up with other aspects as well. Your work as a maintainer doesn't stop when the /src folder is full of code. Then comes the boring part.

These things change from project to project and if a project gets more traction other people will join to fill the missing gaps.

We can expect developers to contain themselves, but some just can't. They are precisely the ones who can't be stopped with any policy. Some are just in a bad mood and they also have graphomania, some are constructive some are mean. I think it's fine as is.

[__derek__]

The first paragraph has the form of the common "toughen up" response to this post, but you hit on the important point: framing matters. Offering constructive criticism is pointless if it's offered under some salt-the-earth banner (e.g., "Angular 2 is terrible"). Empathy costs very little yet helps very much.