1. 28
  1.  

  2. 7

    I stopped reading both r/javascript and hackernews a while ago. But then you kind of have to avoid people on twitter/facebook/whatever else as well. It’s tough to find real articles on dev that aren’t rants one way or the other.

    For the people he’s talking about– it’s just easier to complain than it is to offer any solutions. If they had solutions, they’d probably be submitting them as PRs, not writing rants on their blogs. Part of the problem is the way we tend to see everyone as having an equally important opinion on things. Part of it is that we’re lazy.

    I would say just do what you enjoy doing and ignore the chatter.

    1. 4

      There was a great post awhile back describing complaints without patches as “conduct unbecoming of a hacker”

      1. 5

        I haven’t read the post you mentioned but reporting issues or making suggestions without submitting a patch is of great value (I’m not talking about complaining or ranting). It can help maintainers to:

        • Prioritize feature requests and bug fixes.
        • Understand how users use their software in the wild.
        • Set the long-term direction of the project.
        • Identify parts that are unclear to users which can result in better documentation and/or UI.
    2. 2

      The author, talking about this article: https://meebleforp.com/blog/36/angular-2-is-terrible

      The article goes on to raise a number of issues that they’ve had with Angular 2. The article is sectioned by clickbait-esque headings and filled with angry ranting that barely explains the set of problems they were having.

      That’s just plain false. Anyone who reads the article will find out it was not “filled with angry ranting”. Presumably, the author himself has read the article, so he’s either too emotional to see and think straight, or consciously dishonest.

      Also, the headings in the article can’t serve as clickbait, because you’re already on his site.

      1. 4

        The article uses language like “Angular 2 is terrible”, “That is absolutely bonkers.”, “Unfortunately this is a ridiculously small subset […]”, or “that bold part sounds crazy.” and emotional formatting like “One. Megabyte.”.

        Sounds pretty much like ranting to me. Rant by definition means “long, angry, and impassioned speech”. That article qualifies by my reading. If I am “anyone”, your words are “just plain false”…

        What you are doing sounds like gaslighting to me. Dismissing sombody’s argument by disqualifying their ability to argue at all with words like “too emotional to see and think straight” is basically the textbook definition of gaslighting.

        You are part of the problem the OP laments.

        1. 3

          That’s just plain false. Anyone who reads the article will find out it was not “filled with angry ranting”.

          I read the article. I found out the opposite of your claim.

          Edit: I’m curious as to why I was downvoted as “incorrect” when both statements I made are factually correct.

        2. 1

          when someone starts to insult me in mock my hard work, when they criticize me and my work in a way that is extremely negative, it gets to me. The consequences are horrible.

          Personal insults are bad, I agree with the author on that point. However, when you work on a project that has a large user base, you will get criticism and even rants about your work. Especially in the case of the web, many developers are feeling incredibly tense about the current state of affairs, and whether rightly or not, see the teams of the frameworks they use as responsible for making the web such a hard place to stay relevant.

          When breaking changes are introduced, there will be backlash. Maybe developers should be more polite in venting their frustrations, but some of the author’s referenced articles aren’t even rants.

          But once it was published it was not long before articles popped up that said things like “[Babel 6 is] a lesson in how not to design software” or “[The Babel team] have destroyed the web platform”. I had people mentioning me online saying I was an idiot. A wave of articles about “JavaScript fatigue” started being published.

          I think the author is taking things a little bit out of proportion here. First, the wave of “Javascript Fatigue” articles was not triggered by changes in Babel 6, it was triggered by the acceleration of change in web technology (mostly frameworks, not transpilers) as a whole. Most people don’t even care about their transpiler, as long as it works. In fact, you really have to dig to find negative articles about Babel. A Google search for “Babel 6 is bad” doesn’t even bring up any of the articles the author complains about, and of the results listed only one is actually a criticism of Babel.

          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.

          How is the title an attack on the maintainers? There is a difference between your code and your identity. Insults to projects you have contributed to are not personal insults. This title is a criticism of the Angular project, not of it’s maintainers. The author fails to draw this distinction throughout the article. This is an important distinction to make, because the separation is what helps keep personal biases out of play during code reviews and when giving valid criticism.

          Also, it doesn’t help that javascript maintainers have a track record of not taking feedback from the community. The low barrier to entry I think plays a part in this. It seems like javascript framework maintainers have less of a focus on correctness and in general are more stubborn than framework maintainers in other ecosystems. When your polite discussion gets you nowhere, are you not entitled to vent a bit?