The other day I was in my mind(A.K.A. thinking) and I was thinking about 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. rubber-ducking Javascript Fatigue 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 by (shout out to Kangax by the way). If you haven’t taken a look please do. great tweet kangax In addition to this list mentioned in the above tweet, the following has cropped up: Cli’s (e.g. , ) angular-cli create-react-app Reactive Libraries(e.g. , ) xstream RxJS State Management (e.g. , ) Redux mobX Server to UI Middleware Query Language (e.g. , ) GraphQl Falcor Mobile Platforms (e.g. , ) React Native NativeScript 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 Environment, but expanding to other areas, simply because we can. In addition, as new areas are explored, such as progressive web apps, we find ourselves thinking differently about the tech we build. Thinking about things such as performance, responsiveness, the look and feel isn’t so out of the question. Becoming familiar with apps, such as , , , are part of the quest towards perfection, and as a developer it is something worth learning as well. Invision Sketch Zeplin Which leads to the following, ! We are all aware of the increasing tech in the Javascript eco-system which only becomes larger. We want the app we are currently working on to have it. We know from working on it outside of our day jobs(as most do). This causes the developer to have more intrigue towards Javascript, and less towards the current legacy app, that do not include the above. No state management, no shiny build system, no ES6, or type checking, no query language for the API, no reactive library, no Shadow DOM. These are real issues. Javascript Intrigue These are going to continue to crop up, and they are a major issue for enterprises. Developers will be less interested in your app. In order to increase productivity, the suggestion is to keep an open eye for new tech, as they will save you time as well. I should say I am very happy with the tech at the current company I am working at. However, I feel this article is necessary, as someone needs to express it, because it is a real issue. If you can pass it on to bring awareness, I think that would be great. Thanks for reading and that’s the scoop! The next amazing article is right around the corner and keep being awesome!!!
