Sometimes I think devs are like superheroes who are bored to death and just want to have the greatest world clusterfuck possible to be ... Amused.

Backstory: One project, fairly large (roughly 200 dependencies, a framework). I looked over the ticket backlog and a critical ticket title regarding the important framework caught my eye.

(Rephrased as title was gibberish)

Framework fork needed for supporting different versions of library X

...

Ok. They want to fork a whole fucking framework for a single library dependency.

😶

The framework that is the basis of like 30 - 40 % of all projects at our company.

😶

Maybe.. I just misunderstood it. (my hope dies several times a day, one more or less doesn't matter).

Ticker: Blablablablabla...

"to incorporate library X at version A and - for other projects - at version Y, we need to split the framework into two forks with different versions but same namespace."

🤮

Why. Just why. How the fuck can anyone come up with such an incredible stupidity?

After chewing some people's ears off....

It turned out to be very simple.

Just split off the library dependent part, which were like 20 plus classes.

Release it with two different versions, for library in version A and library B.

Done.

Sometimes devs terrify me.

Please. Never fork / branch a framework or anything "heavy" completely.

That's madness. Properly split what needs to be split and be done.

It's not that hard, hmkay?