Polarized politics has infected EVERYTHING: Part 2 – NPMJS (node package manager)

I work a lot with JavaScript nowadays, specifically Node.js for backend applications.  Despite its unusual single-threaded, asynchronous programming paradigms, JavaScript’s wide adoption and extensibility are the main reasons I choose it over other languages.  The possibilities are endless as JavaScript evolves with current technological trends.

NPMJS (node package manager for JavaScript) is a large database of shared packages within the JavaScript developer community. It is a critical component to the rapid growth of JavaScript in modern cross-platform applications.

The good news is that there is currently a “separation of church and state”.  NPM is open enough that any submitted modules aren’t being discriminated against. Most packages are linked to open source libraries stored in Git repositories. This allows for an increased rate of peer review and testing cycles.  There are no boundaries for creators, so NPM gets the maximum number of ideas flowing in, and the maximum amount of eyes and improvements on the code.

The bad news is that polarized politics is waiting at the border, ready to wreak havoc within.  Tech companies in general have had their upper management infiltrated with ideologues, and NPM is no exception. The CEO of NPM is a victim of postmodernist brainwashing and explicitly shows his political bias. He has been continually trying to merge his church with the state.

If the speaker proposals are all/mostly from white dudes, the quality of content suffers due to a limited pool. This is basic math

Isaac Schuelter, NPM CEO

When you start to see everything by the lines of race and gender, that is prejudice. There is absolutely no need to categorize work based on who the author is and on arbitrarily chosen classifications attached to the author.

When working with npm, I don’t have a clue what race or gender the main contributors are of a package, and I don’t care to know. I’m judging the quality of the code by the code itself. The process is fair and blind.

What Schuelter is proposing here is finding out the race and gender of the once anonymous proposal authors, thereby introducing prejudice into the system. Stereotypes take priority over pure objective analysis of the work.

Even in the 1930’s people paid less attention to these arbitrarily chosen classifications:


Note how this one comment shows how postmodernist infiltration of media and academia has brainwashed people to see everyone in terms of their “class” (race, in this instance). Suggesting the existence of rampant prejudice in society at a time when in reality there was very little creates a self-fulfilling prophecy:

If NPM abandons the free market and embarks a discriminatory censorship parade like YouTube and Facebook, it would likely disrupt JavaScript’s rapid ascent in the software domain. Let’s hope the tech community can start reasoning again from first principles and avoid the pitfalls of mixing polarized politics in its work.

*     *     *

Please bookmark, leave a comment and share if you liked this article.

0 thoughts on “Polarized politics has infected EVERYTHING: Part 2 – NPMJS (node package manager)”

Leave a Reply

Your email address will not be published. Required fields are marked *

%d bloggers like this: