Realizing life's worst problem is the excess of JavaScript libraries
Description
Four - panel pastel comic. Panel 1: a green-skinned, red-sweatered figure stands in a densely packed, bluish crowd; a torn paper caption reads "There are too many people..." Panel 2: the same figure walks past a shop window displaying a red convertible and two cheering humans under graffiti-style text "FUCK YEAH!"; a caption says "Too much greed." Panel 3: the figure strolls through a gloomy landscape of grey clouds, bare trees, and muddy ground; caption: "Too many problems.." Panel 4: the figure contemplates a calm lake flanked by mountains and pink sky; caption: "Definitely too many javascript libraries..." Lower left corner shows social icons and "@PASTILLUSTRATOR"; lower right has the signature "mads 2021" and "www.pastille.no". Technically, the gag equates global existential complaints with the modern developer’s frustration over the endless proliferation of JavaScript packages, dependency sprawl, and framework fatigue that complicate front-end and web development
Comments
20Comment deleted
I miss the days when “adding a button” meant HTML - now it’s a geopolitical summit between React 17, React 18, and three component libraries that each vend their own patched Lodash
The only thing growing faster than node_modules folder size is the number of JavaScript frameworks claiming to solve the problems created by the previous JavaScript frameworks - and we're all just one 'npm audit' away from existential dread
After 20 years in the industry, you realize the alien isn't contemplating the JavaScript ecosystem - they're just trying to pick a date picker library for a simple form. By the time they finish evaluating options, three new frameworks will have been released, two will be deprecated, and the original requirement will have changed to 'just use native HTML5.' The real existential crisis is knowing that somewhere, right now, someone is writing yet another state management library because Redux has 'too much boilerplate.'
The only overpopulation crisis I worry about is in node_modules - my static page has 1,300 transitive deps, three CVEs, and five conflicting opinions on how to parse a date
Left-pad's revenge: one util spawns a universe of deps, each vowing 'no breaking changes' before 2.0 drops
Perspective check: the planet may be crowded, but my npm graph grows superlinearly - one import and I’ve got 4k transitive deps, a dozen CVEs, and a caret that schedules next week’s postmortem
dev_meme.js Comment deleted
best I can do is meme JS https://github.com/agh372/MemeJS Comment deleted
Drinking game: pick a word. If '{your_word}.js' exists, you drink Comment deleted
colonjs Comment deleted
novel.js Comment deleted
guess what https://www.npmjs.com/package/novel-js Comment deleted
yes, I've searched them up. They both exist. Comment deleted
I'm sure exist.js exists as well, but I gtg Comment deleted
yes Comment deleted
not angry, just disappointed https://github.com/shitjs/ShitScript Comment deleted
js.js Comment deleted
Yep, as you may have guessed: https://github.com/jterrace/js.js/ Comment deleted
LOL Comment deleted
This is that babel does also Comment deleted