She: “Execute garden job!”
Me: “Command failed: broken dependency”

Cheap way for space travelling :D

Please stop recommending arch. For real. Stop!

Let's back up. I'm an arch user. Have been for years. I love arch! Like hardcore! But for real, cut it out.

Either they didn't ask and you're being obnoxious or they probably asked "what's a good distro to learn?" Or "Ubuntu holds my hand too much, I want something more consoley" either way, arch is not the answer. Arch is a distro for us stuck up types who like spending all day fixing dependency errors, changing our WM every other week, debating the merits of X vs wayland, and acting better than everyone else.

But here's the thing: I found arch because I wanted something that I could compulsively configure and get really in the weeds. I think most arch users feel that way to some degree. You kinda have to if you want to not be miserable. But many Linux users aren't like that. And that's fine! Let them use mint, or Debian. So they never change their DE. Cinnamon is a great interface! Gnome 2 is totally fine! There's literally nothing wrong with being content with sane defaults and not manually installing every package, and having scheduled releases from a stable source.

Do you tell 7th graders "if you really want to get better at algebra, you should try calculus. You really gain a deep knowledge of math!" No! They will get there when they are good and ready! Or not. It's not a beginner distro. In fact (controversial opinion ahead) it's pretty shitty at being a distro. I have used arch for years! But I don't recommend it to anyone. Because if you want to configure a box for literally 100s of hours (it's never really over is it?), Then you aren't asking anyone about distro recommendations. You've tried them all. You've heard of arch. You been to /r/unixporn.

Stop acting better than everyone else and stop telling people it's better than <other distro here>. It's not. It's different. Very different. And it's not for everyone.

Just received my very first pull request on GitHub. Pull request: "Remove jquery as dependency".

* Makes repo private *

THERE IS A FUCKING DIFFERENCE BETWEEN "React.component" and "React.Component"! Took me fucking 2 hours to figure this fucking thing out. Until then I was certain that this was some dependency issue. Oh the rage right now!! 🔫🔪💣💣😡

Just one more dependency...

When your girlfriend won't stop messaging you...

Colleague: Hey want to get access to our repo so we can see each others code, collaborate, discuss design patterns etc?

Me: Yeah sounds like a great idea. Would love to get to know a bit more about how others are building mobile apps in the company.

Colleague: Heres the link to the iOS app: xxxxxxxxxx

*Opens link*
*looks around a bit*
*Opens cocoapods folder*
*Sees 89 dependencies*

Me: .......... actually, you know what, I have major deadlines coming up. I can't look at this right now. Lets talk in the new year.

*closes slack*

*Adds new dependency*

Me: *Pray while syncing*

*Gradle project sync in progress*

*Gradle build finished in 9s 211ms*

Me: Thank you, Lord

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

Package tsunami 🌊

Ask interviewee what dependency injection is

Starts to explain sql injection..

Don't you love it when there is a new minor release or a critical dependency and it breaks backwards compatibility without mentioning any of it in the changelog or docs?
I absolutely love it! ❤️❤️❤️❤️❤️
I certainly did not waste 3 hours of my life to find it. No i didn't.

Pushed my first own open source project to Pypi as a python package.
Used tox and travis for the first time.

Feeling proud and super content 😊.

I'm in the process of creating another open source package, which has as dependency the first one 😅.

I love Python.

While I was on vacation, someone added jQuery as a dependency to our angular 5 project because all his favorite libraries depend on it.

Some developers get over-excited about using dependency injection and make further maintenance a nightmare.

Fuck all these CSS frameworks using Jquery as their dependency. Cross-browser my ass.

I am going full flexbox.

Other PM: We must fix the database performance issues now.

Me: We can't. We're still only halfway on the dependency chain to tackle this and honestly, even if the dependency chain would be fulfilled, I'd leave at least 2 weeks monitoring the production after the changes were rolled out before we further poke around.

Other PM: This is taking far too long. And whaddya mean by dependency chain? Why was I not informed about this?

Me: *sigh* like in every meeting in the last weeks: the dependency chain are the current open blockers before we can proceed with the database changes. We've talked about this _at length_... Especially why these blockers exist.

Other PM: No, we need to start now. I've _examined_ at the blockers or "dependency chain" as you call it.

(Examined.... He opened on his currently streaming laptop, which was connected to the active beamer, the mentioned ticket with a detailed blocker ... And quickly scrolled. Yeeah. Warmonger...).

Me: I'm very tired of discussing this. But since you are already presenting us the ticket, read out the referenced meeting notes... We explained it in great detail.

Other PM: Why? This is just a waste of time!!!!!!!

--
Yes. This happened. Other PM was my nemesis.
In this meeting were 2 PMs (Him, Me)… I think 5 - 7 devs... And we were sitting in this meeting since 2 hours at least. Everyone was angry...

After this "manifesto of intelligence"… I simply left the room, followed by a few devs.

And yes. Other PM did this on a regular basis....

Application level developer: It's so simple just import that dependency and use that API.

Low level developer : That's cute.

Yesssssssssssssssssssssssssssss, finally!

After months of searching for a damn bug I've finally found it in a 5h session. People increasingly started to worry whether this bug has been introduced because of a recent update of the programming language, but I finally found the bug in a dependency. Nobody thought it would be the dependency, because it wasn't updated in 9 months, but it seems like the update improved the networking a tiny bit, whiche caused a buffer to load a second mesage sooner than expected.

I can finally work on my side project again!
Fucking finally!

I spent the last 2 days resolving over 2k dependency errors in a jee software what used java1.4 libraries

:) i love this profession

Absolutely loving the Slim 3 PHP framework. It's extremely simple, fast, and easily extensible. And nice use of dependency container.

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

circular dependency when you realize you have a

Package not found
Add dependency
Package not found
WTF is wrong with you IntelliJ?!

... 5 Minutes later ...
Oops, wrong module 😥

Manual package/module dependency resolver. Full time.

Well, today I spent the whole day hunting a circular dependency that I introduced and was breaking the whole application.

Fuck me.

Fuck the brains of circular dependency.

On a fresh install of OS X on my hackintosh.
1) Let me install HomeBrew
2) I need Command Line Tools to install HomeBrew
3) Xcode dmg is on my Android. Opens Android File Transfer tool.
4) Error: File is larger than 4GB. Need to use adb.
5) Need to install android-platform-tools, which contains adb.
6) android-platform-tools is available in brew. Goto 1).

Note: Networking is limited to tethering mobile data as Wifi chip hasn't arrived yet.

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!

Maintainer seconds to destroy automated dependency management bot

2k18 colorized

Someone had a question on teams about a circular dependency warning they were getting. They found a work around that would allow it. Someone else responded with this

That moment you receive an email: your CI build is failing.

Ok. What went wrong?

Three new commits that do not seem to alter anything related to the failure.

*reverts commits and tries again*

Still failing.

WTF?!

*restarts previous builds*

They now fail too.

FUCK! BASTARD! Are you kidding me?

*investigates*

Turns out that repo of dependency changed and is not compatible anymore.

Argh! Son of bitch!

They don't tell you this is in uni but your skill in merge conflict and circular dependency resolution is more essential in the real world than your knowledge of data structures.

If you’re writing in Python and you find yourself in dependency management hell and you don’t know about pipenv, consider this a friendly PSA:

pipenv is your friend.

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

God I hate Python dependency management

I hate Python.

Deploying it is annoying, and the fact that I basically need to create another Python instance via 'virtualenv' only so that projects can co-exist without dependency-issues is maddening.

I would be greatfull for Python 3.6+ at least, but NO we're stuck on Python 2.7

That moment when that peculiar fork of a library that one of your colleagues required in a project disappears on github.

That moment you realize the bug is somewhere in a dependency...somewhere...😐

Client: Hey guys! Let us start a bunch of projects that are all dependent on each other and expect them to deliver those on time.

Me: WHAT. THE. ACTUAL. FUCK.

Hit an issue in a dependency of the node library I use, there's been many issue reports on it since october last year and multiple recently (12 days and 4 days ago) - the fix was a one-liner.

All you had to do was check for null in line 17, because in line 9 it gets defaulted to null, but then attempts to null.fetch() in line 21.

Fascinating.

*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

Built my own IoC container for C#. This taught me way too much about SOLID principles and dependency injection that i could give lessons now 😂

I'm still using my own IoC in my projects... It's great 🤘

Compiling software on Linux:

Python interpreter? Easy peasy, just some dependencies here and there. Make does a good job.

Linux kernel? Piece of cake, 20 years of development will be freshly served on your machine after one hour compiling (I have a pretty powerful computer).

Tensorflow? Fuck this shit I am outta.

What is your story with self-built software? Which piece of code has the most terrible dependency hell?

When you feel like your falling behind because at work you don't unit test, use dependency injection or pretty much anything the devs in the community discuss.

Expectation: Today is the last day before holidays and yesterday I completed a complex task, so today I'll have a very relaxing day involving implementing only some simple changes.

Reality: I've just solved a dependency conflict between the project I modified yesterday and another project depending on it that caused the failure of some tests inside the latter panicking my coworkers who quickly asked me "WTF you merged in the core project!?!?"

Yeah, I really need these holidays.

Dependency Injection Frameworks are absolute shit. I have yet to encounter one that doesn't make code take hours to understand or debug, and usually requires a debugger to even begin to unravel it. Not to mention the "context" god objects that just are glorified versions of passing an array from function to function. You guys aren't avoiding global state you're just making it a clusterfuck. Stop being stupid for 2 minutes software development "progress" challenge. Level: impossible.

Many people here rant about the dependency hell (rightly so). I'm doing systems programming for quite some time now and it changed my view on what I consider a dependency.
When you build an application you usually have a system you target and some libraries you use that you consider dependencies.
So the system is basically also a dependency (which is abstracted away in the best case by a framework).
What many people forget are standard libraries and runtimes. Things like strlen, memcpy and so on are not available on many smaller systems but you can provide implementations of them easily. Things like malloc are much harder to provide. On some system there is no heap where you could dynamically allocate from so you have to add some static memory to your application and mimic malloc allocating chunks from this static memory. Sometimes you have a heap but you need to acquire the rights to use it first. malloc doesn't provide an interface for this. It just takes it. So you have to acquire the rights and bring them magically to malloc without the actual application code noticing. So even using only the C standard library or the POSIX API can be a hard to satisfy dependency on some systems. Things like the C++ standard library or the Go runtime are often completely unavailable or only rudimentary.
For those of you aiming to write highly portable embedded applications please keep in mind:
- anything except the bare language features is a dependency
- require small and highly abstracted interfaces, e.g. instead of malloc require a pointer and a size to be given to you application instead of your application taking it
- document your ABI well because that's what many people are porting against (and it makes it easier to interface with other languages)

jQuery. jQuery everywhere.

People's dependency on this library would be like everybody carrying a tool chest with them, even for basic jobs like re-arranging a stack of books or collecting leaves in the yard. Cmon y'all, JS does a lot of this out of the box without the bloated library.

But then again, I'm addicted to MOMENTJS, so I should probably shut up now. 😆😄😬

Learning Angular, starting with a hello world example:

$ ng new wtf
added 1180 packages from 1294 contributors and audited 21849 packages in 18.753s
found 13 vulnerabilities (9 low, 4 high)

Oh, great! Broken from the get-to! But wait, there's more joy!

$ vimdiff wtf/node_modules/is-odd/node_modules/is-number/index.js wtf/node_modules/is-number/index.js

Fresh project, is-odd requires is-number, the project itself requires is-number. And is-number is there twice in two different versions. The notion of a number must have changed drastically in the last couple of years!

Seriously? Angular doesn't even give me the chance to fuck up the dependencies on my own!

When you have a ton of business logic in one of the main services. Good or bad?

>"Maybe I should start upgrading to CakePHP4"
>*dependency hell*
>*solves dependency hell after 6 hours*
>"Finally I can get to work"
>*App has broken all over the place due to app not properly showing deprecations beforehand*
"Motherfuckers"

make code change

stop server

try to re run server

dependency problems

java, tomcat, gradle , eclipse, just kill me, dont torture me like this

As I was refactoring a class in a TypeScript project, I changed calls from `this.config` to `this.getConfig()`.

Suddenly, the tests were failing as somehow the live credentials were used from within the test.

Digging deeper I discovered this.

interface Base {
public config;
public getConfig();
}

So far so good. Wondering why config needs to be public, though nothing too shabby, let's look further:

class MyImpl implements Base {
constructor() {
this.config = this.getConfig()
}

getConfig = () => someGlobalVar;
}

┻━┻︵ \(°□°)/ ︵ ┻━┻

Why would you do this? This breaks dependency injection completely.

In the tests, we were of course doing:

testMe = new MyImpl();
testMe.config = testConfig;

So even though you have a getter, you cannot call it safely as the global var would take precedence. It's rather used as a setter within the constructor. WTF.

Sad part is that this pattern is kept throughout the entire codebase. So yeah for consistency!?

(And yes, I found a quick workaround by doing

getConfig = () => this.config || someGlobalVar;

though still, who in their right mind would do something like this?)

A very good read if you want to learn about dependency injection in .Net. (I might have an older version of the book though)

I think the -f flag in apt-get means "fucking install it". Whenever apt reports some dependency error shit, I'll just do "apt-get install -f" and it magically fucking works.

I hate:
- Enterprise patterns
- Enterprise type programming
- Dependency hell
- Logging hell
- Proxy hell
- Debugging hell

That will be all.

Fuck me. I have to update an Android app I have built 2 years ago. So much have changed, I need to update pretty much every dependency I have and no library seems to compile with the latest Android SDK yet.

I feel like Dr. Strange living the 14,000,605 possibilities when trying different library versions.

It's probably easier to rewrite everything. Now in Kotlin.

The Singleton vs Dependency chain

I wrote an auth today.

Without frameworks. Without dependencies. Without under-the-hood magic. Without abstract pluggable adaptor modules for the third-party auth library with 63 vulnerabilities and 1252 GitHub issues. Without security vulnerabilities showing up in NPM log. Without dependency of a dependency of a dependency using md5 and Math.random() under the hood for historical reasons, and now we're fucked, because this is the only lib for our framework, and we have no time to write our own replacement. Without all that shit.

Rock-solid, on top of scrypt. Stateless and efficient.

It felt amazing.

How could you explain the purpose of dependency injection to 5 years old child?

Why has programming become dependency management and third party paid libraries implementation?

I hate it.

I want to code some real hard stuff but everything is already made!

Me: * Writes half a line of code in an unfinished file *

Me: * Remembers a dependency that has to be installed for this to work *

Me: * composer require thatone/dependency *

Composer: ERROR! Found a syntax error in that one file you were working on, reverting everything you love and removing that dependency that took 10 minutes to install.

:/

This stupid motherfucker just updated a dependency without even realising that it breaks everything, pushed it to the package manager and causes me almost 2 days debugging.

Nico nico wanna break your fucking knee

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.

Spent ten plus years professionally coding, used c, go , python, openwhisk ,docker, kubernetes and God know what else. Now I have to convince those team members who coded so far in their free time that write fucking clean code, avoid dependency on distributed and hard coded configuration, how to build a product
Fuck my life

Welcome to dependency hell.

Spent 4 hours trying to figure out why my expressjs application wasn't working in my environment but DevOps loads it just fine. Turns out there's a difference between ^ and ~ on dependency version requirements. I was loading latest versions of nunjucks and NodeJs instead of stable.

What is life.

When your colleague doesn't add a dependency to package.json and the distribution stops working.
Am I the only one who has got such idiot colleagues? It blows my head every fucking time , I wish I could kill people.

I'm getting stuck in a nodejs dependency hell

Just spent 2-3 hours working on code that's been functional for months, but suddenly stopped working bc an dependency I'd updated decided to change required input/output formats without any documentation whatsoever on those new requirements.

This quote made my day.

"Dependency Injection" is a 25-dollar term for a 5-cent concept. [...] Dependency injection means giving an object its instance variables. [...]."

Websphere...what a piece of shit! IBM, you really should be embarrassed. Dependency injections stops working when the injected bean is in another jar (even though it's on the class path). Works great in JBoss.

Seriously IBM...go out of business already. You are a joke and your products have never been good.

Best : .NET core 1.0 is publicly released

Worst : DI went over my head.

Will try to get it this year.

Vodafone India is so shit omfg

Run npm install, ERROR json parse error due to ssl exception

Run pip install, again ssl exception

Run gradle build, again ssl exception!!!

Now everytime i gotta make a new project or install a dependency in anything, i have to pray to the blood god that cache contains a valid/uncorrupted package dependency or else ill have to nuke cache and borrow internet from someone else.
Once i port it to some other operator, i am gonna incinerate this mf sim.

As someone who didn´t work with dependency injection in almost all projects before:

I legitimately sat here for half an hour and asked myself how to fucking access a new database context...

Me:
You can´t just add that to the constructor.
Dependency Inection:
Yes you can!

Ran the build today 4:30 and found out our grunt file is missing some pretty critical error checks without even logging a warning. A dependency was unavailable and it was pushed to production. The site was down for 30+ minutes.

No sudo on cloud server... Thank you brewlinux you have saved me from dependency hell!

I quietly refactored an entire NodeJS express in-house framework that was written in Java style (dependency injection, inheritance, inversion of control) and split it into typed, composable, parameterized, testable middlewares in 2 weeks (including some complicated ones like a custom Openid Connect flow)

Now comes the hard part: convincing the Java-devs who wrote it that it is useful

Installing a software on Linux can be such a pain sometimes....
This software needs a dependency, which needs another, which in turn needs another......

I mean if you already know you need it, go install it yourself. Why do I need to do everything manually?

And no. A simple apt get install won't work. You need a third party dependency which adds the package to the repository and some other stuff before you can do anything.

Why? Just why?

It was in old days when I was working in java and windows systems.

Java and different log4j versions across dependencies caused system not working only on production server.

Turned out some of libraries got log4j embedded and conflicted with other log4j.

It worked in all computers except production one.

Actually that was my main reason to switch my career to python after that dependency hell.

Another one was windows server 2008 tcp connection limit set to 200 or something.
We needed to change registry to get our servers working. After this case we finally managed to convince people to switch to linux.

Anyway any non standard error when you got multiple layers communicate with each other is hard, practice make it easier to solve those problems as your success moment comes faster.

This is the kind of shit that I don't want to write.
The kind of shit that should be in an STL so I never have to include it in a project.
Because it doesn't belong in a project.
And it doesn't belong in a dependency tree either.
It belongs in a language.

dependency injection is for pussies, real programmer downloads only required library files into tidy folders.

Overhears colleague say 'Ohh there's a plugin for that'. Few weeks later i find the dumb fuck added it to the codebase and not use the dependency manager. I'd happily shoot the senior Dev who peer reviewed it but looks like this pleb merged straight in!

With a codebase overflowing with duplicate frameworks and unused jquery plugins I'll be burning the god damn place down come next week!

Javascript Sucks !!!! Perfect Example of Karma is cyclic dependency in javascript.

That this one component being object orientated is necessary and good design.
We have uh interfaces, theyre contracts.

Spoiler: it wasn't, I could have written it in half the code and half the time. But no, we gotta have those patterns, can't miss on dependency injection!

"Error: Program type already present"

So f--ing what? Ignore the doublon and MOVE ON WITH THE COMPILE, JAVA!

some guy asked me to look at his react project,

I'm yet to find out the problem with his routing but look at this dependency list.

for a simple frontend project, I really dont know how many lazy developers are being introduced into the javascript ecosystem,

might seem normal to others but it feels wrong to me, as a beginner developer who isnt even dealing with a deadline

or......... maybe they are just plain clueless that they dont realize this level of redundancy

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.

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

"You broke the build"

o.O

Me checking the build.

Oh. There's a weird 500 from github.

Oh yeah:

Error 503 first byte timeout

on the package.json of some node dependency.

That's what you get for relying on the cloud.

When you have just spent 2 weeks to build an old workspace, you change the version of technical dependency to start the migration...

I love when a project puts a dependency on infrastructure that has not been implemented internally and have no idea if it will work. *sarcastic voice*

forgot to inject a dependency in Angular -.-

Building a new machine for NodeJS. Installing Gulp-sass has a dependency on node-sass - which has a dependency on node-gyp - which has a dependency ON PYTHON!!!

and.... python 2.7, as it doesn't support 3.0

Doomed - We're all doomed.

Today I could finally spend some time reviewing the merge requests an intern made (and I occasionally helped).

My god, I want to put it this months amount of work an, put it in a trash, burn it and rewrite it before the fire is gone.

5 small and unrelated issues. The intern used branches with the correct naming scheme, but IT'S A FUCKING STRAIGHT LINE BUILDING ON TOP OF EACHOTHER.

Oh ans also they took the liberty to update the dependencies and the language versions used. There was no issue regarding this. It's the first branch in the line and it was called "update_<dependency>" where they just upped the version numbers of everything and then COMMENT OUT all mentions of <dependency> so that it compiles at the very least.

Now today I spend most of my time reviewing the code by fixing that mess. Thanks to updates I had to update the CI and replace some libraries that are now incompatible. Tomorrow I can finally inspect the shit itself.

On a positive side node, I removed node as a dev dependency and the size of the node modules went down from 128mb to 18mb

Hello world,
at my current job at a "big company" our development process sucks, something is on fire at all times, there are hundreds of dependency issues, it's so bad that I'm struggling to find motivation.

Yet they pay me well.. Yaay for big companies that refuse to change when provided with feedback on how to improve things.

Setting up npm private registry and mirror is like setting up machine for handling ddos attack.

Last time I was tuning linux kernel tcp ip stack by adjusting default variable values was ages ago but if you see 100 open sockets in a matter of second after you try to install single frontend dependency you start questioning your life.

"Let's just add a logging system to our dependency"
No. You fucking idiot. DON'T INCLUDE A CUSTOM LOGGING SYSTEM INTO A DEPENDENCY FOR IMAGE MANIPULATION. I DON'T WANT YOUR FUCKING BULLSHIT LOGGING WHEN I'M FUCKING HANDLING IT MYSELF FOR MY ALREADY EXISTING SOFTWARE!! HOW DUMB CAN YOU STUPID MOTHERFUCKER BE TO TELL ME TO JUST "IGNORE" THE MESSAGES IN THE CONSOLE WHEN I'M BUILDING A FUCKING CLI BASED SOFTWARE??!!

I wonder if NPM prevents allowing a package to be it's own dependency. If not I have important trolling business to tend to.

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.

Longtime reader, first time ranter!

I'm just here to complain about how everyone at my company sets "latest" for every dependency.

This wouldn't be the worst thing in the world, expect that no one fucking manages their version numbers...everything is still 1.0.X where X is the build number. Even if there have been breaking changes. Even if it's been like 5 years since the repo was created...

API changes. Customer downloads newest version of dependency, and breaks my software. Why? Because the devs making the dependency don’t phase anything out with deprecation, just poof. So then I’m up all night making a patch so I don’t have to deal with set client.

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.

If I interview one more guy who thinks dependency injection is wholly "those spring annotations" and nothing else, I think I might scream.

God fucking damnit, fuck React Native. Fucking shitpile of weirdass errors, dependency fuckups, fucking weirdass xcode errors.

Proactively seeking out new knowledge: mostly podcasts and watching what's new on github.

keeping an open mind: just because some pattern is industry proven doesn't mean its necessarily the better,

Testing: write a test describing a problem then trying to write slightly different solutions (eg. One that leverages service location, another that emphasize dependency injection..),

Forced & timed breaks: keep hydrated, don't get stuck "spinning the wheel".. :)

!rant
I fucking hate maven and its shitty principles and the pain in the ass it fucking is to fucking use a dependency from another fucking repo that isn't in your fucking artifactory yet and how it can't fucking resolve it even when you downloaded it manually to your fucking m2 cache

React Native so far today:
1. need external dependency to load svg
2. react-native link doesn't work as it should
3. metro bundler not updating its cache

I wonder if the list will grow or that's it for today...

I messed up between Dependency Manager and Dependency Injection and looked a bit of a tool.

Calling any Python programmer here (especially package maintainers)

I run Gentoo, so am responsible for maintaining the dependency tree (to a degree). When it comes to Python I have 2.7, 3.4, 3.5, 3.6 available. I'm always running into some package needing one version or another, and I can't just set a single version and forget it (which is fine. I'm running Gentoo).

I know that this is because python changes rapidly and so different libraries need different versions. Fine.

Why does this happen with Python and not C++, JavaScript, php, ruby, or any other languages on my system? I don't have 3 different versions installed to cover any other languages, and I don't spend time adding installation rules to cover them.

Why does Python need to be a pain in the ass about it?

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 :)

NPM and the whole dependency tree for JS packages should burn in the pits of hell.
Let's pretend that uninstalling a single (albeit larger) module didn't take 8 minutes and that it didn't spit out 20 warnings from a total of 277 (HOLY FUCK) related packages.

How can you guys (JS-only devs) handle this ?!

When your building GCC from scratch and you finally after hours get the damn thing to begin to build it crashes an hour in because of some dependency that is the wrong version! why did the build script not include the check in the first 10 mins COME ON!!!!!!

Took a SWAG at stand-up this morning, saying I thought I could resolve a circular dependency introduced in a junior's branch by noon. As the morning dragged on, I became less and less certain of it, but lo! and behold I managed to refactor my way out of hell with 2 minutes to spare!

This calls for lunch beer! Which management has no way of stopping me from doing on a regular day due to remote working, but at least today I've convinced myself I earned it.

Everyone out here talking about Arch and the setup process. My first experience with Linux was with Slackware Linux. Zero dependency resolution.. Holy shit what a ride that was for my first foray.

Removed a package from my web app yesterday, turns out the package also removes Bootstrap as it's a dependency. TF?! Who removes Bootstrap with an insignificant plugin? Why?!

I would rather create a circular inheritance class for my last task before I'm out of the company. And make some changes to the dependency injection module. Leave it blank documentation. So the one who take my position after me would get enough lesson and reason why he's not to join the company.

the dependency has a dependency with a dependency

God save me from bullets, bombs... and motherfucking Maven dependency management hell!!

On second thought, bring on the bullets and bombs, they're less stressful than this Maven bullshit!!

Me: I have very perfect reason why I did not come to work to day .
Client: Please state your reason .
Me: its silly I don't wanna talk about it.
Client: please do
Me: my index fingers are hurting
Client: why
Me: what do you mean why I was tying to git push heroku master
But every time some json dependency failed

I am amazed how developers avoid to write CSS at all costs! They prefer to struggle with a CSS library than write simple CSS rules.

But the truth is that you cannot even use properly these libraries if you just don't want to understand CSS.

In the end, the result will still look horrible with an extra dependency on the list

Have to write ugly ass wrapper classes around a third party dependency since my team can't be bothered learning its vocabulary. A vocabulary which is very well thought and self-consistent. Apparently, defining our own which is only occasionally more descriptive is preferred. It's already collapsing under the weight of its own maintainability cost. And, if someone joins the team that knows the dependency they are fucked anyway as they'll have to use our wrappers.

Time and time again I've tried to oppose this move on several different merits: maintainability chief amongst them, but no one listens to the lowly new hire.

I should just pipe my thoughts to /dev/null and save my breath...

I've been trying to build docs that worked before for my little project for a fucking week. A problem with dependency, because it couldn't just install for whatever magical reason, although in another repo the dep was installed just perfectly.

A few seconds ago it built. Again, magically.

FUCK THAT FUCKING ECLIPSE DEPENDENCY INJECTION FUCKUP SHIT.

How are you supposed to work with @Preference when it is not in the FUCKING TARGET PLATFORM, and adding it BREAKS THE WHOLE FUCKING PROJECT.

Which update site does it provide anyways for Eclipse Neon!?

Every damn tutorial out there does not talk about that shit or is outdated as fuck!!

AAHHHRRGH! *injects a keyboard as dependency into the FUCKING 💻*

I love C and C++ but their dependency management stuck, there’s a package manager for them which offers a nice experience comparable to Go or Rust?

"npm i {name} - - save-dev"

-ERROR: "{name} needs {dependency} v5.0.1"

"Oh, okay, I install that one then, no problem"

"npm i {dependency@5.0.1} - - save-dev"

-ERROR: "{dependency@5.0.1} needs {dependency} v3.1.1}

"Oh, okay, makes sens I guess, I'll" install that one to then."

"npm i {dependency@3.1.1} - -save-dev"

ERROR:"Nah"

"Son of a.."

WTF kind of bullshit software is sonar.
I can't deploy my application because sonar is telling me that there is a vulnerability. So I look at it. IT'S A FUCKING DEV DEPENDENCY. Are you fucking serious sonar? I can't deploy because a dev dependency has a vulnerability that allows DOS attacks. What the fuck do you think will happen?! I'm going to DOS my own fucking application whilst coding or what? Who the fuck would even care?!
I fucking hate our Pipeline, all the tools behind it operate like shit. the only thing positive about it, is that I am able to deploy applications myself without having to call someone and wait a week. Because putting a file in a directory is hard ._.

Database assisted Dependency Injection... How does that sound?

Not a single year passes that the problem of python2 vs python3, as a dependency, doesn’t bite me in the ass. Node modules frequently fail to build, awscli suddenly can’t find the python it needs because homebrew apparently hard-links to python3 in Cellar... Seriously, W T F?! Fuck you python!!!! You fucking assholes!!! Fuck you and go fucking die!!

Fuck dependency hell.

That is all.

Why does all source code that I see looks like someone just put new things in the file that was opened in the editor at that very moment instead of thinking about where it really belongs?

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?

Android Java came a long way since I've stopped programming for it 5 years ago. Now you've got nice dependency injection, storage helpers and good hybrid solutions. So, curious as I am, I asked to work on some bug fixes in the Android application at work. Bad choice.

"Welcome back!" said the nullpointers, "We've missed you!"

I'm starting day three trying to solve a Dependency Hell issue which is preventing a bug fix being deployed.

Please help.

I spent half of the day trying to make the Grunt script of my node project which uses ECMAscript 6 (Harmony) and make compatible with Uglify-JS by using Babel... Then I found there was a branch of Uglify-JS for Harmony and I only had to update my dependency which took me 2min -_-

See emojis in terminal? Get ready to get 728 dependency security warnings.

From HTML CSS javascript to some voodoo WPF xaml and c#, mvvm and databinding dependency inject cluster bomb to my brain god Microsoft just put a tutorial out like a normal group of people. where you do examples of projects. I'm 2 weeks in and this still makes no sense

Optimizing my RESTful API plugin, used in a CMS to make it headless, was extremely satisfying.
Thanks to caching and alorithm improvements, I brought the response times down by a factor of 150.
The caching also includes dependency tags thus it will automatically invalidate on changes in the dependent element.

Dev: "Oh, btw, I updated our dependency on X since a new version was available."

Almond: "Really?! They only released the last new version yesterday."

Dev: "Oh, I know, but there's a new one now."

Almond: "Ok, fair enough."

*Pulls code*

com.x.x:3.5.1.SNAPSHOT

🤦‍♂️

Going to work with nothing to do because your task has a pending dependency from another team from another country.

Guess i could work on my personal projects so i can actually finish one. Or start another 😁

Dependency injection and RX java and all are cool.

But I like to do good object oriented programming.

And now there are kids in start ups who see devs doing good object oriented programming as retards.

Android as a platform provides everything that you need. Why abuse a simple app with all fancy stuff when you can accomplish stuff with simple oops which takes the same amount of time ?

Am I the one feeling this way ?

What if instead of getting the pfizer or moderna vaccine, you got a VaccineProvider in your arm instead?

Now you can swap out whichever vaccine you like

Let's call it... Dependency Injection

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!!

So I was planning to use an REST API wrapper library and I included into my app spent over an hour working my logic... No errors... but then when I compile... I get a FUCKING DEPENDENCY COMPATIBILITY ERROR.... My NET Framework app isn't compatible with NET Standard libraries??? WTF.....

Anyone else here who really enjoys writing pure functions or domain classes?

It's so amazing to be able to write dependency-less classes that have such simple, elegant logic and sometimes just a bunch of getters and setters. Pure functions with type hints are also one of my favorites.

Does anyone hate debugging something for a couple of hours just to find out it was you misspelling something that somehow managed to not cause an error?

Also what are the worst things to have that cause a error? Like dependency being outdated and not being notified etc.

Getting settled on a new team. They are using this custom built Dependency manager/Build tool. I’ve now wasted 2 weeks trying to get it up and I haven’t started my actual issue item yet.... sigh I wish I was on the team that uses Gradle.

Tech Lead = "Super quick question" + "one small doubt" back to back for 8 hours, then coding in the evening because making some progress is the only way to take the stress away. Rinse and repeat, while slowly developing an alcohol dependency. Be kind to your leads, kids.

Fuck you Spring and your stupid cryptic, useless, no relevant information error messages.

"Oh I am crashing violently because some of my internal component cannot automagically talk to another my internal component" says spring.

Well shit, why do I let you manage your own dependencies if I still need to hunt down what garbage transitive dependency you bring in 5 time.

YOU HAD ONE JOB!!!

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.

Well, I thought "hey, I need to urgently update my own infra for a change, been neglecting this way too long, but should not be longer then a day."

I spent the whole weekend dependency resolving, modulesyncing and ensure deps are met ... And every single goddamn time it's stdlib causing a whoupsie on another module...

Oh at least I am having fun. Sort of.

Multi-threaded dependency downloads are a blessing.

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.

My visceral hate of Spring.Net burns with the force of a thousand suns.

Almost everything it does is done wrong or solved better by other solutions.

Specifying which classes to instantiate from .xml files? Sure why not, compile type safety (the whole reason for using a static programming language) is obviously overrated and dependency based injection is surely impossible!
And for extra bonus points, now our client code must be aware of the internals of the service classes, and all of their references as well, because, encapsulation? Who cares.

Have you made an typo? Good fucking luck finding out from which of the 100 config files we have floating around...

And, because it has baked in AOP and Transactions its woven into the fabric of the project like a tapewom.

Of course this may just be how our "special snowflake" project uses Spring.

What makes it more painful is that I love good DI tools (ninject, castlewindsor, autofac, there are so many...) and we're stuck with this turd because 7 years ago some java devs couldn't be arsed to learn a new library...

> As a developer in the Go world, I would recommend you to embrace idiomatic Go patterns and avoid dependency injection.

google literally created a DI lib for go.

Fast XML parser - fastest XML parser in nodjs without any dependency

Fighting a CDI dependency injection problem that makes no sense. The only thing that sucks about the magic of DI is troubleshooting it when it doesn't work.

Bought fucking nvidia gpu to test speed of some fucking machine learning models that generate speech.

6 hours wasted already for installing fucking dependencies
cuda, fucking tensorflow gpu, bezel and other shit

Fucking resetting password to download deb with cudnn,

really ??????? fucking emails are not delivered to my fucking mailbox

After mass click of send email and multiple account ban and unban I figured out I should login to nvidia website and then allow access to fucking developer every time I want to log in there - fuck shit

Uninstalling everything now looking for fucking compatible versions between software.

10 years in this business still fucking installation of dependencies is most difficult part

Fucking corporate business and their shitty installation instructions to fuck up peoples lives and switch them to the cloud.

Same was with fucking kubernetes

Fucking software dependency hell

It’s worse then ever before.

Fuck ....

I'm getting pretty fed up with dependency injection and having to do work in Loopback; why cant it just work!

Python dependency rage 😡

Whatever, as long as it has 0 dependency to mainframe 💩 directly or not
Fuck mainframe up it's dusty ass

The bipolar nature of leading a startup tech team:

It's either no one needs you, or the problem is big enough to have you push 5 fundamental fixes from abyss to upstream.

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...

I know that DI(dependency injection) is probably just another good pattern out there like many others, but dear lord have I been burned on it with acumatica. Acumatica just loves having friggen magic crap everywhere with no damn explanation(*may be in a blog post somewhere but that’s no replacement for good documentation).

I believe they use AutoFac in C# on an asp.net server. They love to utilize reflection and injection and in turn the server takes multiple minutes to startup whilst it dynamically registers everything, as well on any individual pages.

Development is a pain in the ass on this damn system.

I’m constantly having to dive into the damn code using dotpeek to understand what the fuck they are doing and it’s often friggen stupid shit. They like to reinvent the wheel a fair bit.

Dependency on Microsoft

Composer dependency not found

[!dev], [toasters]
Does everyone only ever toast perfectly uniform slices of bread?
My grandma has a toaster that has two doors which open to the side and are held closed by a spring. This way if a slice is too thick the door can't close properly, but the damn thing still works. It's from before ww2, like most dead simple devices that work surprisingly well. I can't find anything similar anymore. The only two types now are the top-loaded design that simply doesn't work with thick slices, and the version for Americans or families of twelve that is the form factor of a smaller oven. (Which I obviously don't have room for. I already have an oven.)

Btw, how should I tag this? It's a rant, but it has nothing to do with the platform except perhaps the undocumented dependency between toasters and bread slicing machines.

Everytime I go back to native Android, I end up: -Wasting a lot of hours with gradle and the shitty dependency system.
-Doing a couple of cours of actual coding and finishing what I needed to do.
-Swearing to never come back

Couldn't sleep most of the night because was thinking about dependency injection (Spring) and unit testing...

And came to the thinking that pretty much every time you need to create a new method it should be in a new class, wrapped with and interface?

So then how do you decide whether to create a new class/interface vs a private method in an existing class?

Threading gui's and sockets...
What a painful day...

I honestly hate python dependency hell.

Started coding in python 2 months back, currently working on a distributed alarm system using rpi3's spent the whole day figuring out how to use it all without them all crashing into one another...

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

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

Node Js Typescript dependency management makes me want to hang myself

Spent an entire workday yesterday getting a project out of (unnecessary) dependency hell. Today it's actually still working. Imagine that.

Next job I find has to be entertaining somewhat. I thought I could deal with boring work but I'm tired of it.I It's just so damn boring. I'm not even writing new code anymore, I'm just updating dependency versioning and restructuring tests. It's bumming me out seriously. The mental fatigue from struggling to keep my eyes open every day leaves me struggling to get out of bed in the morning.

I hope people don't use container to workaround dependency issues. That's like buying a new computer because you don't know how to upgrade a tiny software. We should learn how to manage things properly, not wrapping shits up and pretend it is clean

Why is it that every time I want to make some dead simple script with Python it turns into the utmost awful programming experience?

Ah no you see you have to install this dependency but even if pip doesn't give you an error your script will still crash on import and vomit up some ugly back trace that doesn't tell you anything.

And then some retarded sub sub dependency wants to run on Python 2 and that has its entire own shithole of dependency hell.

And then for some unknown reason the Python installation wasn't compiled with zlib and some library wants it so you either you compile the entire thing yourself or idk go fuck yourself?

Why is this hot mess of a language still in use? I dont get it, it's easier to set up a cmake project with C++ for gods sake.

I just read about the npm dependency incident and was confused at how someone could create a package that brings so much dependency and simply have the right to delete it? How many other vital packages can be deleted?

i'm starting to like reactjs over vanilla, but i can't help but remember how it suffers on npm's dependency hell. i mean just look at what happened before at left-pad. it makes you feel like the entire system is so fragile.

And there I was thinking Maven is going to make life simpler, with this granular dependency management and IDE independence (no extraneous classpath and module management required). But wait, it turns out that to run simple Ant task I need all my dependencies to have *.pom. Every. Fricking. Dependency.
I mean, sure, only if I knew which sub-dependencies they all had, but that seems like heck a lot of work to make external JAR libraries to work with Maven process.
WHY TODAY? Yesterday I had no issue: uploaded few libraries in corporate repository, refreshed index, dependencies downloaded, even had time appending javadoc to one of them and it worked. But today is the day, right? I just run simple task with maven-antrun-plugin (mvn antrun:run@<executionID>), and it starts scanning each dependency for *.pom file. I DON'T WANT THIS. Google, help me. Oh, no direct answers and clues?

Just... fuck you, Maven. With all 2 days effort I could just litter in IDE's classpath, write build.xml in no time, make normal webservice, but that would require me to also litter sources with required libraries. FML!

Our company has a hierarchy where there are core modules that are to be included as a dependency in large end products. There are two end products.

One of my coworkers just included one end product as a dependency in the other and pushed.

Work proxy, meet dependency hell.

Can't even install pip modules, everything has to be done through source 😓

I hate AndroidStudio when it adds constraint-layout as a dependency in my build script whenever I create a new Activity.

Visual studio. The lockups are incredibly annoying, the codebase's dependency on its toolset is worrying, and the inability for me to customize it deeply conflicts with how I work as a developer. It costs so much and yet the man hour cost of moving our codebase out of it is way more, so we are trapped

I wanted to continue working on my project at my grandparents house, using my laptop.

I've pushed the most recent code, but what I didn't push was the recent commits I made in my helper library...

I was updating and using the library locally and now I have a dependency on ../library name. Great job me

And the finale of my day was spending an hour + trying to figure out why a Java program with outside dependency loading runs in Eclipse but not CMD....

I mean seriously, learning dependency injection using dagger 2 was unnecessarily hard wtf.

Started doing CakePHP because of a project I’m taking over. What in the world is that? Dependency injection? Separation of concern? Single responsibility? What did I get myself into…

Tmw your angular app just stops working because of a mandatory circular dependency you simply cannot get around.
yay!