There is no yummy when you npm install express and even if there were, the code shown would certainly not like a tweet as the POST is not authenticated.
And the author has described himself as "JavaScript clickbait enthusiast."
Someone doesn't get satire. This article is clearly not meant to be taken serious and the number of car parts is therefore by far not the only incorrect fact.
the whole "oh god, excessive dependencies mean js is gonna die!" response that people had at the time, which was imo more due to their dislike of JS as opposed to the dependency management
Honestly, there isn't much a narrative here. I just want to make people put their egos aside and laugh. I've written a few other articles in this style: https://medium.com/friendship-dot-js
In a way, I'm interjecting myself into some sort of "great debate" (dependencies are nuts! web frontend tooling is nuts! CSS is the worst!) and just poking fun at both sides. Planting myself firmly in the middle, without much of an opinion, just making sure we don't take ourselves too seriously.
They're fun to write because it's really a stream of consciousness. I don't edit the posts, I don't fix typos. So it's public therapy in that regard.
I know real good programmers, who ride on the "don't reinvent the wheel" train to the max.
And while the code base don't get cluttered with "ad hoc informally-specified bug-ridden slow implementation[s] of half of Common Lisp" we implemented ourself, we now have hundrets of modules, which themself probably contain this "ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp"
18 comments
[ 4.8 ms ] story [ 48.8 ms ] threadNow I'm curious how many of top 100 popular npm packages include the same shady monetization?
There is no yummy when you npm install express and even if there were, the code shown would certainly not like a tweet as the POST is not authenticated.
And the author has described himself as "JavaScript clickbait enthusiast."
A joke? Bad one?
Do you know what your language is doing in the background? Or your database? Or your web server? Or kernel? Or your CPU?
To tell obvious lies about node_modules in particular, IMHO, does not serve any purpose in raising the awareness about that particular problem.
Someone doesn't know anything about cars.
the whole "oh god, excessive dependencies mean js is gonna die!" response that people had at the time, which was imo more due to their dislike of JS as opposed to the dependency management
In a way, I'm interjecting myself into some sort of "great debate" (dependencies are nuts! web frontend tooling is nuts! CSS is the worst!) and just poking fun at both sides. Planting myself firmly in the middle, without much of an opinion, just making sure we don't take ourselves too seriously.
They're fun to write because it's really a stream of consciousness. I don't edit the posts, I don't fix typos. So it's public therapy in that regard.
Also note how the author's tagline is 'javascript clickbait enthusiast' :-)
I know real good programmers, who ride on the "don't reinvent the wheel" train to the max.
And while the code base don't get cluttered with "ad hoc informally-specified bug-ridden slow implementation[s] of half of Common Lisp" we implemented ourself, we now have hundrets of modules, which themself probably contain this "ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp"