friggin' node dependencies

Today, after two hours of debugging, my girlfriend called me to break up.

Then my backend started giving strange errors about some unmet dependencies.

I believe by the time Elon Musk sets up a colony on Mars, npm will be done installing those fucking dependencies.

When all project dependencies can be installed using apt-get...

Co Worker: "Your computer is missing a mouse!"
Me: "I require less dependencies to use a computer"

BBUUUURRRRNN

I just hate npm dependencies.

If you want to write a small website with npm dependencies (some frontend deps like Bootstrap and some development deps like gulp or babel) you will have more npm dependencies in your project than own code. It is ridiculous, how some lazy developers just add dependencies to their projects, without evaluating their dependencies. The source code of one of my projects is around 4MB (without any dependencies). If you then run yarn as required, it grows to around 80MB (where 73MB are node_modules).

This is just terrible.

I rant about this, as I made the mistake to upload my node_modules directories when restoring a backup of my server. Worst idea one could ever have.

<rant data-type="corny">

My Gf of 3 years left me for some douche. Thus said, she "removed" her feelings before kissing him. WTF! I didn't know feeling came like dependencies...

</rant>

There is code reuse and then there is stupidity. This npm module has 4 dependents and 2 dependencies.

Saturday plan: serious switch to Linux.
1. Installs Fedora, lookin nice.
2. Let's update it, fails to boot.
3. Nouveau driver fails, lets install proprietary one.
4. dnf install dependencies, repo returns 503
5. Be stuck on a 640x480 bash.
6. Boot windows, start overwatch.

Just need to install some dependencies

Dev1: We need you to name this service
Dev2: Name it whatever
Dev1: You should name it
Dev2: Can we change it later?
Dev1: No
Dev2: Are you going to have dependencies on the name
Dev1: Yes
Dev2: Call it StupidDev1
Dev1: Ok we will name it

When you can't remove an app cause one of its dependencies depends on itself

FUCKING FUCK JAVASCRIPT AND IT'S FUCKING 10000 DEVDEPENDENCIES.

LET ME FUCKING CODE AND WRITE TESTS AND NOT SPEND FUCKING ONE FUCKITY FUCK WEEK TRYING TO FIGURE OUT HOW TO FUCKING MAKE MOCHA AND KARMA PLAY WITH FUCKING ES6 CODE YOU FUCKING FUCKTARD PIECE OF SHIT TECH.

I NO LONGER FUCKING KNOW WHICH PACKAGES I FUCKING NEED AND WHICH I FUCKING DON'T FUCKING DUMBFUCK FUCKWIT OPEN AND HACKABLE MY BROWN ASS PIECE OF TECHNOLOGY STACK.

[14 dependencies]

"Geez this project has a lot of dependencies. I know, I should use a package manager!"

[15 dependencies]

Welcome to javascript kids!

Emotional roller coaster today.

+ Got first pull request! Hell yeah!

- oh, no, no no no nononono, they pushed all dependencies and temp folders...

fck sake isak, gather yourself

Dependencies here dependencies there, dependencies fucking everywhere.

Hey look, npm broke my project again. Surprise!

Code and dependencies on my local machine, all untouched for a couple of weeks, no longer works. I've no idea how it even managed that.

Oh, and `npm update` crashes.

eventually solved by upgrading npm and running `npm update --depth 500` because some arbitrary child dependencies changed without updating the parent packages, ofc. on my local machine. without me having run `npm update` for about a month.

because of course that makes sense.
Second time in two months, too.

isn't npm great?

Arguing over PRs with juniors who try to push unnecessary badly maintained dependencies, which are in fact just turds wrapped in startup hypespeak, because they're too lazy to actually invent some non-square wheels.

When you about to start a project by doing a small module, but as you code, you keep thinking about scalability, security dependencies and such....

....three hours later, you still haven't written code

1kb of code
14Mb of dependencies
Interesting...
Welcome to Node.js I guess.

When every time your coworker start a new project, they just use the template out of the box including the sass, less and other unused dependencies eventhough they don’t use it

Installing all the needed Latex dependencies on linux takes maybe 15 seconds, on windows I need 5GB of space and it takes forever to install.

Loaded morning dependencies 😬

A conversation that me and my boss had this week:
Boss: "Hey, why is this not progressing"
Arcsector: - "We're waiting on system users to move their destinations"
"We need the system in the database in order to move it"
- "Okay awesome - let's move it, oh wait, I can't do it because I don't have access, here's the stuff that needs to be done: a, b, and c"
"Oh I'm actually not able to help with that"
- "So then how are we supposed to get it done?"
"idk but also this other issue is something missions are complaining about"
- "oh I already am talking to them about it and it should be remedied by the team creating the problem because it's a false positive"
"Well we need to solve it still"
- "We would've solved it already but it has dependencies with other projects that we're still working on because we don't have enough people"
"We cant get you more people because we don't have the budget"
- "Then this stuff will have to wait"
"Get it done"

ACTUALLY SCREAMING! Why cant people understand that there are conesequences for their actions??!!

"The hardest part in programming is installing what you need."-the guy that almost threw it's PC out of the window because he spent 2 hours installing the wrong version of opencv

When you're about to install a small program (54mb) and you need 1gig of dependencies. And the dependencies need two gigs of dependencies of their own. Proprietary piece of shit. Grrrrrrrrrrrrrr

Code snippets without dependencies ❤️

Just run “npm install”.

Mother fucker, if that worked, or if the six hours I spent trying to unfuck your dependencies worked, we would not be having this conversation.

I just removed a couple of packages from package.json and my compiled war went from 53 MB to 37 MB.

What the heck are you downloading node? I don't like such bloated packages.

$ npm install ...
$ added 10 packages from 7 contributors and audited 21813 packages.

I realized that after some point you don't even think about your project dependencies growing. Because even adding 10 packages, it looks like it doesn't even changes the total number of packages. 21813, 21920, 21980... Does it even matter? Fuck.

Kevin, we use the v2 of the Java AWS SDK. Stop dragging in your crappy v1 dependencies, in many cases *duplicating* the bloody v2 dependencies anyway, because, I quote:

"Stackoverflow and AWS don't seem to have many examples using the v2 SDK though"

Use your bloody brain and figure it out, Kevin.

Never remove Python (and its dependencies) from Ubuntu.... I'm not proud...

unpopular opinion: javascript has broken standards, and nobody corrects it. people use these frameworks and shit with 600 dependencies, then can't figure out how to update their application when things go out of date. now people are expecting you to use NPM to make a - - > static <- - website

Optimization trick.
The client shared this!

`npx create-react-app blah`
`cdls blah && npm audit`

63 vulnerabilities.
good fucking job.

To be fair, they're all minor, but they're all *exactly* the same, caused by the same freaking package. Update your dependencies already!

------

`npm i --save formik && npm audit`
68 vulnerabilities, three of them critical.

ugh.

Wow!
Makefiles are SO much cooler than I thought before

$< = the first dependency file
$^ = all the dependency files
$@ = the build target

AND if I try to build something who's dependencies don't exist, it'll automatically try to build them!

When npm modules bring in 1500 micro dependencies for a service you could build in 15 minutes, it makes you wonder if you should, in fact, rebuild the wheel.

Plus 247 errors and dependencies.

How I wasted my Sunday:

A programmer I know claimed that his Nodejs app was lightweight since it only relied on 2 dependencies (express and mongodb)

So I wrote a script to recursively transverse the npm dependency tree and count the number of dependencies there actually is

Installing those 2 packages alone means your app depends on 73 pieces of software in total

In conclusion, nothing written in Node is ever lightweight

Oh yeah, it was also Easter I guess

You've got to be a masochist to be a javascript/typescript developer.

Each time I come back to the npm-related parts of my project, the application won't start because of some dependencies nonsense. And I know for sure I left the project working perfectly last time.

Every time... every fucking time! Just leave the project unattended for a week and be sure you'll find it dead next time.

I mean I as a developer don't really have to do ANYTHING for my code to break.

How can people love javascript is a mystery to me.

Time spent during a nodejs project:
- 2-4 hours trying to install modules and dependencies.
- 1 hour actual coding!

MARKETING IS A MENACE FOR SOCIETY and a large waste of time and resources.

Imagine that for some very stupid reason people were allowed to steal cell phones from unsuspecting victims and sell it on open market legally, tax invoices and all.

One could create a business like this. Steal some lad's brand new $600 iPhone and sell it for $280, because why not?

That is marketing. A company goes and makes a phone for lets say $180. Add in taxes, shipping and development costs, and we get to $300. Put some real nice profits on top (let's say 40%) and we get to $420.
The last 180 are the cost of marketing for society.

Today some stupid marketing conmen goosesteps into my lab and says that we must use Tensorflow and in-memory databases and multicloud redundancy and, I kid you not, "profound learning".
WE HAVE A FREAKING LOGISTICS OPS APPLICATION.
"We are putting it on the brochure, those technologies are set to sell well in our core market, and improve employer-branding" says the conmen.

A request for a feature is one thing, a request for an whole other technology because some snake-oil salesmen read the term in some clickbait rag and thinks that some starry-eyed moneyhead will pay extra because the brochure says "NOW WITH 2X MORE TECH!" is just an assault on society.

Node.js: 3 dependencies, 8448 depents ... GG

When you look through your team’s custom protocols to figure out which one you need, and someone has not only made a massive typo, they then DOUBLED DOWN on the typo and made a bunch of dependencies based on that typo.

As in, the word “downloadable” spelled three completely different ways, and EACH ONE is treated like a different class with its own attached dependencies.

AND THE COMMIT MESSAGE ATTACHED IS “lots of cool stuff.” HOW IS THAT A COMMIT MESSAGE? WHICH ONE DO I USE?!

I’m never finishing this ticket, I’m going to get fired, etc. 😡😡😡😡😡

"note that the package name is different from the importable name"

God I hate Python dependency management

I've never been more glad for ubuntu on Windows. Python dependencies (through babun) were fuckin' me left, right and centre.

I freakin' love this message...
Welcome to the dependencies hell.

When configuring a digitalocean server and install shit loads of dependencies takes less time than npm install .....

I fucking hate frontend development
>updates three dependencies for security reasons
>entire thing falls apart
>spends whole week to fix it
>its literally just two lines to fix it but those lazy mfs had to ask a QA to rewrite it
>mfw

Today I got a segmentation fault in C#.

No pointers. No unmanaged dependencies. Just managed code. Seg fault.

Uhhhh...

when the junior dev updates all npm & nuget dependencies in the project to the latest beta versions to make an impression right after joining the project...

Name a more iconic duo than web developers on help sites and having pissing contests over which modules they use instead of actually answering the question!

I've been a web dev/server admin for all of about a month now, and only known PHP for about a week of that, and the one thing really that grates on me isn't PHP's odd function naming inconsistencies or at times outright trash documentation, it's the other developers who, when asked a fairly straightforward question about why a mysqli function won't return something, demand you use PDO instead.

Please. I'm running a LEMP stack on a Raspberry Pi here, I'm trying to keep dependencies to an absolute minimum because the SD card is tiny, the Pi will catch on fire if it runs any hotter, and more dependencies are more potential points of failure. Just answer the damn question. I'm not going to install PDO for something I know I can do anyway just because it makes my code look slightly prettier.

Honourable mention to all you Node.js developers out there too, with your thousands of useless npm dependencies. I salute you.

Hey if you make an app that specifically depends on gnome and has 2 gigs of dependencies on other platforms

fuck you fuck your ancestors fuck your entire extended family fuck everything you have, do and will ever stand for, i hope you contract ever imaginable diseases to the point where existence itself pains you.

I really like Docker. I think that’s the best thing that happened in the dev field for years. Easy shipping and installation of software without messing up dependencies to other software.

Removing Node dependencies 🥂

Turns out our PHP dependencies are installed with NPM instead of Composer

People say, "Yarn is faster", blah blah blah and so on. So, I thought, I should give it a try. So, I tried and Holy Fucking SHIT! It took almost half an hour to download the dependencies! :|

Just realizing now that I've probably spent 60% of my programmer age (years of experience) waiting for dependencies to install and praying that the 9 kB/s connection I'm struggling with remains alive every single fucking time otherwise I have to start the wait all over. 😡😡😡

How the fuck do you people develop on Windows? 30GB of Visual Studio dependencies to get a compiler going, now this???

If only we could only download the entire internet and cache it in a disk at home

THEN I WOULDN'T HAVE TO FUCKING RECONNECT TO READ SIMPLE DOCUMENTATION EVERY FUCKING TIME MY INTERNET DROPS

I'M NOT DOWNLOADING A MILLION DEPENDENCIES I'M JUST READING STACKOVERFLOW, FIX THE INTERNET FUCK

NPM has this cool feature called "link" which allows you to easily link local npm packages as dependencies of other local packages for developement. It's so cool in fact that everything you run npm install it deletes all your links for fuck all reason

Fuck npm and its mess with dependencies 🙄

The joys of having NPM put all my dependencies sub-dependencies in my modules folder ☺️🔫

Web dev in 2016:

Keep installing node dependencies until it works.

The one thing more annoying than my girlfriend is the chain of mail I get from Github saying,

"One of your dependencies has a security vulnerability."

Why has web development become so complicated?

I'm learning React with JSX . Why is JSX even necessary? HTML works fine. Its simple and gets the job done.

I can't stand the node_modules directory either. Opening it up reveals what seems like hundreds it not thousands of dependencies that all have their own recursive node_modules folder and the dependencies continue.

Why are we creating more unnecessary abstractions on top of more unnecessary abstractions? What happened to K.I.S.S?

What was wrong with vanilla Javascript and becoming great at that and using just that?

Dev nightmares :

- Not finding bug fix on stackoverflow/GitHub .

- Losing code that hasn't been pushed to GitHub.

- Dealing with an unclean and inconsistent database.

- Installing Node Dependencies.

- Resolving CORS and 500s.

- Training a Linear Regression Model with 700 epochs on an entry-level Laptop.

Keep appending to this list.

#devrant #devnightmares

I like my work, don't get me wrong, but any time I need to work with this fucking 12 years old project that has so many conflicting branches, css that remembers float layouts, half of the files not being tracked, ruby dependencies that are a decade outdated I just want to quit.

*needs to repartition disks
*is mounted, need live usb
*download and burn gparted live, ≈20min
*reboot, usb not bootable
*try again, maybe it's corrupt...
* nope it just won't boot
*download and burn puppy Linux ≈20min
*is bootable
*installs gparted
*opens gparted
*repartition disks
*NOPE
*e2fsck failed: get a newer version of e2fsck
*already the latest version
*hmmm, maybe if I build it myself
*dependency hell
*dependency hell
*dependency hell
*give up
*download and burn Debian live ≈40min
*try to install gparted
*can't get WiFi drivers working
*give up
*download and burn Ubuntu
*opens gparted (already installed)
*partitions disk, leaves to complete overnight (it will have to move ≈60GiB)
*comes back in morning
*computer went to sleep after 10 mins
*late to work but oh well I at least got it done

Getting nugets and dependencies of a big project to restore properly (most of the time the dev fcks his solution up - it works for 'him')

You just realize the sheer amount of dependencies spring boot has, when maven tries to resolve them while sitting in a train with bad wifi

Fuck nuget, .NET and whole C#, I'm solving problem with dependencies since yesterday.

Developers who think complex code is good.

"Oh, lookie here, I can swizzle methods and inject dependencies in the runtime!"

"Although we have no valid use case, let's use dependency injection and follow the commandory stateor patterns because I watched a video."

Just because you learn something new that looks cool does not make it practical, you tosser.

I love python, but I hate dealing with python dependencies, especially on Windows.
I was tinkering and researching with neural networks, so I wanted to try out pybrain. I wrote my project, with pybrain installed via pip, and tried to build it.
Oh, what's that? Pybrain doesn't work with python 3? Well I'll download the version that's supposed to. Oh, that version has a deprecated numpy api? Let me just install those other resources. Oh, that requires a broken module that has no publicly available source?
Let's try python 2. Oh, now that's working, I just need to export environment variables for some "bls source". Some quick Google searching and the only solution that would work is building a bunch of cywgin modules by hand. That's fine, I have an ubuntu partition.
An hour later I'm compiling FORTRAN dependencies on Ubuntu.
Coding time: 1 hour
Dependency time: 3 hours

I miss the ease of installing shit on Windows, none of this missing dependencies nonsense!

Wordpress updates > breaks jQuery dependencies
Requests theme update > theme update upgrades database without asking
Database upgrade breaks child theme > spending 30 mins rebuilding the filestructure and database from a backup

God, I hate python and its ecosystem with a passion! I feel like because of it being so popular amongst non-programmers 99% of the python code one has to deal with is just plain garbage. Also, fuck your shitload of dependencies who all fail to install!

Fuck third-party's third-party dependencies which break your third-party dependencies

A co-worker was running into a little permission issue with some dependencies and my reflex was to say, "chmod dat hoe!".

I don't like when depending on something, e.g. smoking or coffee, but
still have to carry on dependencies in node_modules.

Installing some dependencies with a tool from the company
« Error »

I click on More Details.
It was blank.
Thanks. Helpful as always 👌

This week I’ve been reinstating IE11 support.

OMFG WHY!? I hear you ask.

Is it due to critical legacy integration dependencies? AD Intranet logins? Draconian Group Policy rules?

Nope. This ONE user just prefers it! 🤯

How much are we getting paid for this nonsense? Sweet FA!

#cognativedissonance 😢

When learning new tech, it takes me forever to get the environment/dependencies setup because of the million different errors I get.

Am I just too dumb to follow installation instructions?

Why python can't into proper dependency management?

I Node.js we use npm. Modules are downloaded per project and packaging is easy.

In Java we use maven/gradle. Never been so easy to build and download libraries and package your project.

But in Python? No, it's not easy. You have to use virtualenv first so pip/anaconda won't download globally, then you must write setyp.py in a million different ways. Packaging and distribution to clients? Good luck with that.

Dependencies and backwards compatibility

Can shit just fucking work instead of me having to download old shit that doesnt fucking work on the newest version of the OS that I use because the fucking program can't use new dependencies?

I'm looking at you you fucks that don't want to update to VS 2019 and force me to uninstall it to download VS 2015, its 4 years old for fuck sake!

I hate dependencies... I'm stuck on a project because I need to wait for some one else to provide specs and access to their API.... And well I was also given a deadline...

When you want to move your site off of jQuery, but all the dependencies still use jQuery.

Also screw those services that write their client code with jQuery. Screw you all!

I love the simplicity of jQuery and Angular 1.0 - you just include the JS files and off you go. No additional dependencies or messing around.

I have the habit of adding //todo comments to my code whenever I need to implement something later. Very useful to just search your code for "todo" and see what is left to do.

That is all very well, but I just searched my project for "todo" and there are SO MANY //todo comments in the third party dependencies...

>ooo new thing to play with and learn, yay!
>*Installs using directions*
>Hello world program fails
>Oh I need these dependencies
>Wait the deps all need their own deps...
>But one of them is deprecated.. what do?

I love the feeling of working on something new but
I hate ending up spending more time getting a workflow setup and chasing down random bugs or hacky fixes just to get something stable so I can start working!!!

I want a tool called "bogo-npm" which creates a VM and then installs random versions of npm and dependencies in a cycle until the build is successful. It'll probably be the biggest optimization that dogshit ecosystem has ever seen.

I'd just let it run over night and save myself the urges to strangle every single fucking developer who added dozens of dependencies to a stupid near-static website.
And the creator of the abomination called `npm uninstall` which for some fucking reason does the same as `npm install` and then obviously fails because that's the reason I wanted to remove that package in the first place.

We need more heroes like that leftpad dude.

Nothing's as fun as unraveling the mystery of how a certain dependency got pulled in transitively....

In a monolith.

With over 1000 dependencies.

Kinda like sorting rice by the size of each grain.

Things that make a friday entertaining.

💩💩💩💩💩💩💩💩💩💩💩💩💩💩

I don't consider myself a guru in JavaScript (hell I studied theoretical chemistry), but I do hate much of the rationalization behind building a Jenga stack of libraries, frameworks, dependencies... for building everything web related.

Many of the problems I see people solving with these giant stacks could be easily solved understanding how websites work (html, css, js and how interact with each other) with no dependencies giving smaller (for end users at least) and more maintainable code (in the sense it would not require updating dependencies that may be discontinued...)

I do imagine situations where these are ideal... Since there are not absolutes and developing is very context sensitive, but man if I have js article fatigue for ridiculous scenarios.

I would like to stop and genuinely thank the devs and anyone that contributed to NW.js for allowing users to work outside the sandbox. Fucking sandboxes these days make developing editors and tooling a bunch of bullshit hassle. I understand why, but it makes an entire class of software that much more difficult to develop.

And on a semirelated note, I decided to go with nw.js because unlike electron, I don't have to tell users "just install these two gigabytes of npm dependencies *from off the net after already downloading the main application*, dependencies that could break at any time at all for any reason."

Does anyone even bundle their dependencies any more or is this something only clinically insane people like myself do?

Because last I checked most users still don't know how to debug console autobarf when a single command goes awry due to something obscure like a version conflict between two brittle cogs in the organ grinder known as package management.

Edit: also, nw.js startup times and memory requirements are relatively sane compared to electron.

That moment when you realize you lost control of everything ¯\_(ツ)_/¯

brew install node

keeps going for more than 5 minutes, installing idk dependencies or doing idk wtf

fuck javascript and its ecosystem

When you spend half the work day and skipping lunch to resolve dependencies and process packages for an API but realize you're using the wrong OS…

Wtf does it even make sense to ask devs to do estimates for the spike, planning and the implementation of a big feature containing other features which nobody has any idea how long it will take to do and what are the dependencies and to try to fit it in the next quarter release?

Agile my ass.

Had a 5 hour call today, where we wanted to set up a system from one of our subcontractors in our own environment. Struggled forever to get the backend up and running.
Turns out that some dependencies were hardcoded as local file URLs...
No, our linux machine does not have C:\Users\<username> 🙄

I think this DDoS attack has made a few people re-evaluate their runtime dependencies

I'm getting caught up on my personal project because I need to generate a lot of Dynamic HTML using JS and it's just a pain. I hate adding dependencies to a project, especially personal projects with no deadlines, so tomorrow I will be writing a vanilla templating system, and hopefully that will un-funk me.

Fucking love how one-liner packages are breaking basically the entire JS ecosystem every once in a while. Why the fuck do you add one-liner packages as dependencies in your code?

Dependency hell is the largest problem in Linux.

On Windows, I just download an executeable (.exe) file, and it just works like a charm! But Linux sometimes needs me to install dependencies.

At one point, I nearly broke my operating system while trying to solve dependencies. I noticed that some existing applications refused to start due to some GLIBC error gore. I thought to myself "that thing ain't gonna boot the next time", so I had to restore the /usr/lib/x86_64-linux-gnu/ folder from a backup.

And then there is a new level of lunacy called "conflicting dependencies". I never had such an error on Windows. But when I wanted to try out both vsftpd and proFTPd on Linux, I get this error, whereas on Windows, I simply download an .exe file and it WORKS! Even on Android OS, I simply install an APK file of Amaze File Manager or Primitive FTPd or both and it WORKS! Both in under a minute. But on Linux, I get this crap. Sure, Linux has many benefits, but if one can't simply install a program without encountering cryptic errors that take half a day to troubleshoot and could cause new whack-a-mole-style errors, Linux's poor market share is no surprise.

Someone asked "Why not create portable applications" on Unix/Linux StackExchange. Portable applications can not just be copied on flash drives and to other computers, but allow easily installing multiple versions on a system. A web developer might do so to test compatibility with older browsers. Here is an answer to that question:

> The major argument [for shared libraries] is security, that if there is a vulnerability in a commonly-used library, then only that library has to be updated […] you don't have to have 4 different versions of a library installed

I just want my software to work! Period. I don't mind having multiple versions of libraries, I simply want it to WORK! To hell with "good reasons" for why it doesn't, and then being surprised why Linux has a poor market share. Want to boost Linux market share? SOLVE THIS DAMN ISSUE!.

Understand that the average computer user wants stuff to work out of the box, like it does in Windows.

Almost 800MB of dependencies just to download the damn npm, sometimes I wonder if some part of the software developement world is going crazy

I was in dependency hell for two days.
Im a junior working in a team creating an ember app. Suddenly a main component refuses to work since an addon threw "EmberObject undefined"... Nobody could reproduce it and we where out of ideas, so I tried fixing it for 2days (7h total). I finally got it working after updating yarn :D
It never felt so good working again :)

Watch out for that Event Horizon

The codebase Im working with is like someone took 3 sets of earphones, crumpled them together in their pocket, and then threw them into a bag full of spaghetti and wasps. Too confusing to comprehend and dependencies absolutely everywhere. All I have to do is port over a relatively straightforward piece of functionality from one iOS app to another. Core Data has other plans it seems....

Our company has a giant folder that you have to download every release. It contains all of the dependencies within the company and every config file.

Twice a month your workspace gets fucked...BECAUSE THESE FUCKING GENIUSES CANNOT USE FUCKING MAVEN! What the fuck?! What idiot came up with this stupid idea?

the dependency has a dependency with a dependency

Company Infrastructure Team: We are doing away with proprietary libraries and using standard Java instead.

Also Company Infrastructure Team: Here have a fuck ton of new proprietary libraries with dozens of nested dependencies. Oh we don’t use Maven by the way because we are fucking idiots.

Most of the times I feel like I install stuff for longer than I code... Just random thoughts.

Installing 1 NPM package...

350 more dependencies installed :D

A quick rant about dependency injection.

I see far too often in projects, a huge over-reliance on dependency injection / IOC frameworks which permeate throughout the entire codebase.

I cringe every time I see a constructor annotated with @Inject and 10 params.

The benefit of these frameworks is how easy they make it to manage many dependencies. What I dislike about them, is exactly that. I feel that they make it TOO easy to manage many dependencies.

How trivial is it to simply add another constructor param? exactly. And people then wonder why their dependency tree looks insane.

I am a strong believer in injecting dependencies the traditional way, via the constructor with no fancy framework. The reason being that it forces you to think more about the dependencies you are adding to your classes, and consider if they are really all needed.

The other problem I have with it, is it basically encourages you to inject everything because its so easy. The purpose of dependency injection is inversion of control and allowing classes to depend on abstraction rather than concrete implementation. All that goes out the window when you @Inject 6 different concrete classes.

Use dependency injection for its intended purpose, not as an excuse to be lazy and avoid thinking about dependencies.

I tried to install a simple Python package today for a simple 10 line program and spent over an hour installing dependencies and reading documentation.

I've sat with this shitty bug since 9:00 this morning. Just finished fixing it. What could causing such a fatal problem you may ask? Not pinning fucking dependencies.

*facepalm*

Python is really beginning to turn horrible now. Legacy codes...argh!! why don't developers move already to python3? and all those horrible third party dependencies for only 2 which somehow break after even some mending. God save them. Horrible night.

Am I the only one who very often creates a new project folder and copies all the code because it's easier than cleaning dependencies and such?

Reading someone's legacy package.json
{
.... stuff
"licence": ....,
"dependencies": { .... },
"bugs": "run for the hills"
.....
}
what is this? am I supposed to find an issue tracker in some unnamed hills

When you have assigned stories that are blocked by other dependencies being developed in the same Sprint... Oh boy, someone is not going to finish on time u.u

If you are using arch and are making packages from the aur all I can say is use makepkg -s because then it will install all the dependencies for you.
Yay

Our Swift teacher at college manually creates a Podfile for every project and copies and pastes the basic initialization from an existing project, pastes the cocoapod dependencies and then installs them using terminal instead of just doing a pod init and then using nano or vim to paste the dependencies right inside the terminal. These are the times I genuinely feel sad for the way Indian education system is and the way we're taught coding in colleges here.

-- Who are we?
#Developers.

-- What we want?
A #stable project environment.

-- What do we say to project #dependencies?
Never again!

Our configuration manager is leaving for a new job and now the office is crumbling.

How do you deal with person dependencies at your workplace?

CAN 👏 PEOPLE 👏 STOP 👏 ADDING 👏 `/// <reference lib="dom">` 👏 TO 👏 NODE.JS 👏 PACKAGES

It's a Node.JS package, for fuck's sake. But for SOME reason, sometimes to get around the lack of `URL` and `URLSearchParams` in @types/node, people keep including the *entire* DOM typings in their definition files/TypeScript files!

Sometimes I upgrade my deps in a Node.JS project and find that DOM typings have been added, causing errors when trying to use the global `URL`/`URLSearchParams` (I've shimmed these so that these (Node.JS versions) are in the global namespace). Then you have to search in all your dependencies for which one is including the DOM definitions.

when you install a module on limited internet connection and it comes with over 50 dependencies

Want to download maven project dependencies but too lazy to google the right command.

Chaotic good: building an electron app and pulling all the other dependencies from cdn

So I had someone question why their system was broken after they installed my software and all of its dependencies to /usr by hand... ._.

If your unit test has a bunch of mocked up dependencies which you puppet to do whatever the fuck you want. Something could be improved perhaps

- write a test at a lower level if possible where the dependencies can be abstracted away, or you pass down what you need from them
- write a higher level integration test, i.e. which uses real spring context instead of mock dependencies

But my senior tells me that a unit test will almost always mock all of its dependencies, it should only test the logic in it's tiny atomic piece of work. Mock everythign else out.

Devrant, how do you unit test? I'm looking to learn more on the topic and hear how others do it.

Do you prefer to pin dependencies to an exact version or a specified major, latest minor version?

What if life was on git? Where you can simply create new branches of it, stash shit, remove dumb people with dependencies and finally the ability to turn back time with this version control.

Docker is about handing over the weight of your incompetence in managing dependencies to your customer.

Saw a git repo that contains the node_modules folder and some dependencies and was wondering how'd fuck did this guy get this up here.... Mehn some devs can be super powerful(funny)

Fuck not-so-old-but-deprecated-nontheless-software! And their also deprecated dependencies.

We're using a year old dotnet version which apparently only works with a specific libicu version.
Then there is node.js, but it has to be version 6 otherwise nothing will work.
If you wish to use VS code you have to manually install a specific version of the c# extension and keep it from auto-updating because project.json is deprecated and not a thing anymore.
Migration is not an option, it fucks the whole project.
I mean it is a great project and all, but the dependencies are driving me crazy!
Why does stuff get deprecated so quickly?

Managing dependencies with npm or yarn feels like trying to communicate with a bunch of hipster kids. "Ugh omg I no longer hang in that namespace like that was so two weeks ago"

Managing countless dependencies makes me wonder if we can escape the madness and return to the simplicity of vanilla JS. Must be better than being doomed wandering the labyrinth, right? 🤔🔄🕸️

Do you know that lady who waits in line at the grocery store for ages and when it's finally her turn she suddenly realizes that she might need her wallet somewhere from the bottom of her bag?

That's our current business analyst managing external dependencies like a boss... :D

A client project came with a bunch of references missing, and nuget wasn't properly restoring them. I've just spent most of my weekend trawling through the dependencies, extracting them from their nuget packages, and putting them in the appropriate folders manually.

Slowly developing a horrid hatred of nuget...

Why the fucking nuget needs a Microsoft/whatever account and asks for it every 3 seconds? FUCK YOU, you can just install dependencies manually without any fucking account why you fucking bug people perpetually with login screens

I fucking hate working with older software

I have a visual installer project, and it automatically finds the dependencies to make the setup file.

if I rebuild a certain reference, in which I made no changes, and then refresh the dependencies, it will add another dependency that already exists, but outside the dependency folder. So now I have two exactly fucking the same dependencies.

i can remove it, but removing it doesn't change any of my files. So there is nothing to commit. If you restart the project, its back.

And first it required me to actually add the dll to the build folder before it would build. And suddenly not anymore.

Im pretty sure its either the outdated installer software or visual studio 2013 fucking with me.

It also randomly added a dependency from blend. Which is apparently a known bug, but never got fixed in the two updates after they recognized it as a bug.
Fuxx you microsoft...

Can someone please force my project manager to use fucking Maven for dependencies instead of including local jar files for some side projects?
And possibly a better IDE than Netbeans...

Each time I have many dependencies in the project

I cannot for the life of me get the debugger working in RubyMine because debase gem wont install. WHY AM I WASTING TIME DEBUGGING THE DEBUGGER INSTALLATION?

Dependencies are just someone else’s code.

- Need a module to work with PDFs
- npm install
- But wait, that requires some dependencies
- And those dependencies require more dependencies
- Python not found
- Issues with env variables and wsl
*Bajillion hours later*
- poppler-qt5 not found
What the hecc is a poppler and why do I need it?
:/

C++ circular dependencies.. Gave up debugging on that so many times

Thanks to my parents to create an Application Context and autowire all my Dependencies required to live a happy life.. !!! The best framework that provides IOC -- Parents.
Note: Finally understood spring framework IOC and DI concept.. many more to understand..

Dependency hell - when you have a package you want to update and then you find out 3 other things depend on that version of that dependency and then your pretty much screwed so you just leave the original version of the package you were trying to update in place.

Installing a deb file on Manjaro. 😐

Tried Docker...over complicated
Tried dpkg... dependencies nonexistent in manjaro.

Snap packages?
Appimages?

How to update a react native project:
1. Run react-native-git-upgrade
2. Notice that your project dependencies are mucked up
3. Try to fix node modules and the build process
4. Find out the moon landing was a hoax, wait what?!
5. Use react-native-init to create a new (working) project
6. Copy code files and dependencies to new project
7. Wait for new version :)

Taking into account the way npm manages dependencies, how many modules do you think I had to include to download the whole npm?

Node developers are something else, you can work on a project that is 2 years old and find abandonware dependencies that were last updated 4 years ago.

should i add to an existing horrible node js program with dependencies that are marked unsafe or no longer supported, or port to a nice shiny c# or python app that will probably be much easier to support and extend and organize ?

2 weeks is now wasted.

Sr. developer wrote code but didn't checked in all of them. now it won't compile because of its dependencies from other class.

Sr. developer went on vacation for two weeks

So our webserver teacher have been throwing around the idea that before installing anything on a Ubuntu Sever, you should run apt-get update (yes you should)

But, he also instructed everyone to run apt-get upgrade as well (in case some dependencies need to be updated)

Now for fucks sake:::::
1) apt will automatically sort out dependencies when you install a new program
2) you never ever efffing fucking wanna run apt-get upgrade on a live server. I'm not a sysadmin, but this seems like a really fucking bad idea, right?

"dependencies not satisfied" = code for countless trips to Stackoverflow and Askubuntu

installing kendo ui in an application we've worked hard on slimming down. package count for getting datagrids up and running you ask? 12; direct dependencies, mind you. FML

When you download whole SDK, install lots of dependencies. Setup everything. And the moment you want to start working, your internet stop working. I would consider that a sign from a good but too bad, I am atheist.

When you're writing your most beautiful module yet and realize that you need the new Jackson library, go to upgrade the dependency and all your old dependencies break because nobody ever took the time to keep packages up to date! #DependencyHell

Trying to figure out what the fuck and why I did some stuff in gradle dependencies to get shit to work

joke is I didn't understand it back then anyway and was just following some documentation to get shit to work

Dear Python linters, why can't any of you implement some actual linting features? Like, say, consistent use of single or double quotes? Or dict() vs {}? How about indenting nested function calls? Forcing list / set / dict literals as multiline? Trailing commas?

And while I'm at it, why can't you handle dependencies properly? Say, separating linter & linter plugins from the remaining dependencies in a way where I don't have to manually remove them from the requirements lockfile every time?

This week has gone from Vue.js to jQuery to Angular.js.

Not to mention untangling various npm dependencies for each project!

Started working with a startup. They have one Dev guy, who for some reason is using both python 3 and 2 in the same git repo, and had no requirement.txt or anything to really track dependencies....

For fuck sake, the Dev guy is actually intelligent, but really freaking messy.. why can't he have this basic thing done...

That feeling when...

...you can't build a project because you can't autogenerate some files because they rely on some other autogenerated files that rely on some other autogenerated files that can't be generated because the project can't build...

Just another day in the eye of the dependency hurricane!

Make your code available for your team members, please.

So we're working on this robotics project using ROS, a framework that enables multiple nodes in a network exchange their functionality among each other through tcp connections. Each node can be implemented and executed on your own machine, and tested with dummy inputs, but in collaboration they make a robot do fancy stuff.

The knowledgebase needs data from the image processing unit, providing this data to others with semantic context to high level planning, which uses this semantic data for decision making and calling the robot manipulation node with meaningful input, to navigate the robot's components in the environment. We use a dedicated machine, which pulls the corresponding repositories and is always kept configured correctly, to run each node, such that everybody has access to each other's work when needed.

So far so good. We tried to convince the manipulation guy (let's call him John) to run his code on our central machine, not a week, but since the first day, 5 months ago. Our cluster classification has been unavailable for 2 months, but my collegue fixed that. We still can't run the whole project without John's computer. If his machine blows up we're fucked.

Each milestone feels like a big-bang-test, fixing issues in interfaces last-minute. We see the whole demo just moments before our supervisors arrive at the door.

I just hope he doesn't get hit by a truck.

React native dependencies hell is killing me

Fucking dependencies

npm has to be the single worst package manager on the planet... Trusting devs to use semantic versioning properly and forcing devs to trust authors of dependencies to use it properly is nothing short of insane. The package-lock that is "supposed to be version controlled" causes *constant* merge conflicts. Using shrinkwrap in its place is borderline useless because it Doesn't. Lock. High. Level. Dependencies.

I don't know who designed this, but I want to give them a very bad day for every hour I've spent trying to lock versions correctly on a live project.

Not to mention requiring root by default to install things that can just run whatever they want is ludicrous.

If you publish a package over Composer - or in fact any package manager that allows optional dependencies - please don't make dependencies that aren't **absolutely necessary** required.

Is it a theme for your nice app? Don't make it required, some are not going to want to use this theme and don't want to deploy extra Megabytes to their servers every single time.

In fact, someone may even want to replace that dependency with a fork, like a customized version of that theme because it is not flexible enough! Forcing that dependency means it can only be replaced with hacks.

I am looking at you, `oxid-esales/oxideshop-metapackage-ce`, with your extra themes and demoshop data that makes the Deployer tool push and copy around half a Gigabyte of unused assets on a website every single deployment!!

That feeling when your project is ready and you are figuring out how to build and executable JAR with too many dependencies.

I'm a C# dev, I'm used to updating all my package dependencies by clicking on one button "Update All", and it's done.
I was consulting for another project written in python, it seems there's no way to update libraries like that due to circular dependency hell. Is it so?

Finally I understand the frustrations that is packages and dependencies in npm...

I have never really used node.js, only on windows to help develop a chrome plugin, but trying to do the same thing on Linux, omfg, how is it this bad?

On Windows I just ran the alias "npm start" and is figured out that it needed to install a bunch of stuff, did it and continued compiling.
On Linux I just got one missing dependencie after another... How is it that different?

figured maybe you can specify dependencies specifically to be used in main.rs (as a standalone executable) or lib.rs (as a library)

since for some reason there's dev-dependencies which specifies they will only be used in tests or whatever

well rust actually doesn't compile code that wasn't ever called / would be run (and nags you about code you have but didn't use anywhere). this means binaries are smaller and all that. i've known about this but seemingly the AI insists nobody needs to specify dependency differences between main.rs and lib.rs because of this quirk of rust compiling

ok well then why the hell is there a dev dependencies and a normal dependencies then?

well no good reason.
- "intentionality" -- how about the clarity of intentionality between being an executable or a library?! no? guess not
- build optimization, because traversing usability graphs can be taxing especially in big projects. ok. again still applies to executable vs library problem
- "community and ecosystem practices". really? we've always done it this way? shove it 🙄😩. you try to innovative and then willfully inherit the problems you solved of other languages... because that's how we've always done it. lame

double standards. so annoying

All of these dependency management tools supposed to make my life easier?!?! I have been looking for half an hour for how to simply downgrade a package to an older version I must be plain retarded

Is there actually any frontend framework or boilerplate to just code and avoid messing around with old libraries, missing dependencies, no documentation? I'm seriously moving to plain ES6, it feels more flexible :/

Hmm. I've been wondering how I'll deploy an api based on a microservice style the smartest way... The general plan was to use salt to setup the base server and install dependencies and add the configuration.. Doing updates would be a git pull and pm2 restart api. I would love to know how you deploy your software ?

So I upgraded the dependencies to the latest version - and it’s all gone to hell. Of course it has...

My project is a cloud based automated testing product. My current story is to extend a module to support multiple of a particular testcase type in one test run instead of just one. This has uncovered a rats nest of complexity because everything is designed with the assumption that there will only ever be one of these testcases.
Refactoring about 5 different classes just to get into a state where i can pass a list of testcases into a service instead of just one. Wrecking my head...

Well, I just finished resolving the problems with my Angular dependencies. It has been 3 days of trying to come up with the solution, and in the end, it was all a matter of version mismatch of three dependencies. Now I can (actually) get to work on my project.

That Feeling when Eclipse removes Maven dependencies, put his compiler and Build Path to Java 5 when you're with Java 8, and cookies aren't good since it's not yours.

Yay for git

Dependencies suck.

I wanted a ruby gem and needed an older version of ruby to run it. Fine, what's the best way to get multiple ruby versions on one system, apparently rvm.

Now I want rvm.

I can't have rvm without getting gnupg first though.

Before I can get gnupg I need brew.

Now I have brew setting my computer on fire compiling god knows what so it can get gnupg so I can get rvm so I can get the ruby version I want to get the gem I want!

It's been running for quite a while...

This isn't the first or last time that the convenience of packages and versions leads to a maze like trail of prerequisites you need to follow.

I'm sure there's some tool that would've helped with my problem, but the problem shouldn't be this bad to begin with!

I understand why it happens but it still sucks and it's a lot of wasted time.

Frankly I'm expecting some people will have gotten so used to this kind of insanity that they won't get why I'm renting about it, oh well, it made me feel better and gave me something to do while brew is melting my machine.

This feeling when you're fighting with an issue for few days and accidentaly find out the problem is caused by a dependency of the library you're using... And someone reported it already few weeks ago... Just kill me.

Was learning c++ really fast,but I stopped because I just can't find a way to deploy the applications with their dependant libraries on linux.cant I just include the .so files in the same directory as my executable.

Seriously, fuck Bazel. It's the most unintuitive build tool I have ever had the displeasure of coming across.

It works, but try compiling an Android app, that uses deps from gmaven, maven and jcenter and has java, as well as native dependencies.

It's fucking impossible.