Dependency bloat stories

File: 4918770424_63beeb742d_z.jpg (121KB, 500x589px) Image search: [Google]

121KB, 500x589px

>want an evernote close because behind nazi firewall
>try out one based on rails
>install dependences
>340mb, 100k files
>need toolkit to compile native mumbo jumbos
>get the right toolkit from ruby
>continue the build
>fails to native compile shit even though it managed to compile some of it
>"screw it"
>let's try these ones made on node.js
>npm install
>240mb, 60k files
>"are you fucking real"
>one page app, looks ugly
>left column with groups is bugged and you lose the subgroup if you append the parent into another group
>overengineered code for so little features
>delete
>windows complains about too long paths and can't remove everything without handholding
>make it stop
>try the other one
>same shit, but at least it only takes 40mb
>literally just shows notes in a bar and a textarea on the right
>doesn't even have persistence

What the fuck is wrong with these people ?

How can you need 140 dependences for a fucking note taking app ?!
How on earth can they bloat to one hundred fucking thousand files ?
What the fuck is wrong with these shitty dependency managers, how is that possible that they download the whole fucking repository.

What the fuck is this babel hard-on that these turbo-hipster developers have these days.
Just to use the fucking ES6 import export they have to retardify everything with useless transpilers and shit, when node already supports most of the specs ?!?

Why these module developers can't get their shit together and do things properly, it's almost like they think that bringing a hundreds of files for a single module is a reasonable idea. And importing modules that import seven hundreds more modules is for some reason acceptable.

And most of all, how on earth can you need all 50mb of shit to make such a basic shitty barebone app that can be done manually with maximum 2-3 minified libraries and a few lines of HTML and javascript ?


Share your stories.