Javascript Intrigue

The other day I was rubber-ducking in my mind(A.K.A. thinking) and I was thinking about Javascript Fatigue once again. I realized that I haven’t really seen anyone talk about the flip side of Javascript Fatigue, and I think it is important. So let’s talk about it.

Before you go ahead and try to think what the flip side of Javascript Fatigue is, here it is. Javascript Fatigue is very unique to the Javascript Environment. There are many new tools that one has to learn, and will constantly have to learn on a consistent basis. There is a great tweet by kangax(shout out to Kangax by the way). If you haven’t taken a look please do.

In addition to this list mentioned in the above tweet, the following has cropped up:

1. Cli’s (e.g. angular-cli, create-react-app)
2. Reactive Libraries(e.g. xstream, RxJS)
3. State Management (e.g. Redux, mobX)
4. Server to UI Middleware Query Language (e.g. GraphQl, Falcor)
5. Mobile Platforms (e.g. React Native, NativeScript)
6. Story Book

Not to mention that the majority of the tools in the above tweet’s info graph(I can’t believe I am referring to a tweet, but I am) have and are growing exponentially. Also, as a Javascript Engineer(specialist) as we get to do more, as we can accomplish more, things like creating our own API’s, or virtual boxes(e.g. Docker), aren’t out of the question. We find ourselves, not only learning new things within the Javascript…