I'm upvoting this because he sounds angry and it has a clickbaity title.
Joking aside, I agree with what this author says. I'm a small open source contributor with a few of my own projects. Nothing huge, but I could imagine the frustration involved in pouring your life into a project just to get it shit on by armchair programmers. They often don't understand the complications involved in your decisions. While we should all be aware that these developers are making these comments because they've probably wasted their life trying to use a project which wasn't designed to solve their problem, like a square peg in a round hole.
I myself have become frustrated by many things, particularly how coffeescript and ruby are so lackadaisical in their syntax compared to JavaScript even, but I don't go and write articles about it. That's my personal preference, not something I want to force upon the world. I've considered writing one but I can't hate it enough to divulge my frustration on others. It would be a waste of my time when it would just be easier to avoid it in my own projects.
Regarding the way we have to compile JavaScript now, this is a natural evolution of professional development. First we start with simple kids websites, then we learn and want it to do more so we add things, like angular 2. Then we realize that angular and react are application frameworks, so we have to add things like Babel. This is how it works, the more complex you get, the more preparation you need in terms of utilities. These utilities are still new, so they don't always work well together, but that's just growing pains. Nobody complains about the c++ build process, or Java, or C#. These are application languages and they have compilation steps. JavaScript is nearly the same nowadays.
0
u/Buckwheat469 Dec 05 '16
I'm upvoting this because he sounds angry and it has a clickbaity title.
Joking aside, I agree with what this author says. I'm a small open source contributor with a few of my own projects. Nothing huge, but I could imagine the frustration involved in pouring your life into a project just to get it shit on by armchair programmers. They often don't understand the complications involved in your decisions. While we should all be aware that these developers are making these comments because they've probably wasted their life trying to use a project which wasn't designed to solve their problem, like a square peg in a round hole.
I myself have become frustrated by many things, particularly how coffeescript and ruby are so lackadaisical in their syntax compared to JavaScript even, but I don't go and write articles about it. That's my personal preference, not something I want to force upon the world. I've considered writing one but I can't hate it enough to divulge my frustration on others. It would be a waste of my time when it would just be easier to avoid it in my own projects.
Regarding the way we have to compile JavaScript now, this is a natural evolution of professional development. First we start with simple kids websites, then we learn and want it to do more so we add things, like angular 2. Then we realize that angular and react are application frameworks, so we have to add things like Babel. This is how it works, the more complex you get, the more preparation you need in terms of utilities. These utilities are still new, so they don't always work well together, but that's just growing pains. Nobody complains about the c++ build process, or Java, or C#. These are application languages and they have compilation steps. JavaScript is nearly the same nowadays.