Echo JS 0.11.0

<~>

xat 212 days ago. link 5 points
The React community is lucky to have Dan :)
planttheidea 211 days ago. link 3 points
The JavaScript community is lucky to have him, the man is a hero.
goliatone 211 days ago. link 2 points
While it's nice that someone took the time to write a response  and while it does address everything React related in the original article I'm not sure is making a true argument addressing the underlying critique of the original article- or other similar articles. 

What I understood to be the real critique of the original article: JavaScript fatigue, see [this old article from 2015] (https://medium.com/@ericclemmons/javascript-fatigue-48d4011b6fc4.)
ryanwild 205 days ago. link 2 points
JavaScript fatigue is self induced what I don't understand is why everyone feels so pressured, no one is asking developers to learn all the frameworks most companies stick to the top three and each have their own ecosystem
goliatone 199 days ago. link 2 points
I agree from a personal stand point that JavaScript fatigue can be self induced. As an example, in my spare time I like to pick up new trends and play with new frameworks or libraries as much as I can. I'm lucky in that professionally I have a high degree of autonomy and I can control the "speed of change" at which new things get adopted and how change affects me.

However, I hear a lot of people exposing very articulate arguments and compelling stories about JavaScript fatigue. And I can understand where they are coming from. But because I am privileged enough as to not be burned out by how quickly "things" change I would not go as far as to say that people who feel that fatigue should blame themselves.

Without putting too much effort I can think of a few situations leading to people feeling this way in which they have no control.

My point was that the article did not address this in any way.
goliatone 210 days ago. link 1 point
Yes, that was the link. Comments seem to not fully recognize the links and stop at the username