> When we launched Babel 6, we made an API change that we had planned for awhile. We moved from having an implicit (“works out of the box”) behavior to an explicit (“will work for everyone”) behavior.

Just like Rich Hickey said in his last talk (see https://news.ycombinator.com/item?id=13085952), breaking changes are broken. For greater good or not, it's no surprise people complain when you break their code/workflow.

> I want to talk to you about an article that was written the other day titled “Angular 2 is terrible”. For starters, that title alone is an attack on the maintainers. Surely the author wants a set of problems addressed. But why should the maintainers want to even click on that link, let alone try to address the problems?

I too think that Angular 2 is terrible. It is not an attack on the maintainers, it is just a piece of (IMO) bad technology with maintainers feeling attached to it.

It is a very crucial skill in life to be able to withstand critique and take it to your advantage. There is a lot of usually unnoticed utility hidden in critique, waiting for someone to reap its benefits.