Dependency Hell, Monorepos and beyond

[@CharlieBelvo18]

Great talk. I love the idea of seeing who consumes your API, and combining your new JAR file with their code to see if it builds successfully, then deploying in the consumer app automatically.

[@maximilianorios]

The same exact case at 10:07 happens to us right now, we have around 30 versions of a service and it's nearly impossible to understand which one to use. In fact, we are stuck in a version (let's say 7) when the 12 is available but the subsequent versions have degradation of performance in some cases, or break too many things or it changes the way of querying causing a ripple effect on too many things.

[@tenminutetokyo2643]

Easy? Everyone has made the web overcomplicated. Simple should be the first and most important design principle. Can we please consolidate stuff, people?

[@triularity]

@12:49 - But you can have multiple versions of classes loaded, IF you use compartmentalized class loaders. As long as multiple versions can run side by side and not interfere with each other (e.g. they don't open a static named temp file which can't be used by more than one version, or instance, at the same time). And also as long as the libraries using different versions keep them hidden, thus incompatible sub-libraries can never directly interact by being exposed to each other.

[@BrianHayesOfficial]

Documentation. Actually answer the “why” and “how” in your docs. If critical thinking is our job, then strive to provide the tools to allow people to critically think. Document why you have the dependencies you have. That way the person there while you’re on vacation have an actual source to refer to as to why things exist as they do. It blows my mind how little documentation exists in a way to do anything more than provide a basic “just do this and it works!” Example. Make your docs in a fashion that would make you understand how it was written without you having any prior knowledge. I get the demand, but even comments all throughout code can making everyone’s lives better

[@triularity]

The funny thing is, I had this problem, in principle, solved over a decade ago.. or at the very least greatly reduce version conflict issues. I even publish some ideas and library code based on those principles several years before this video was posted. But since I'm a nobody and the code was on a personal nobody server instead of some well known site, like github or wordpress, I expect few, if anyone ever took notice of my work. And since I'm not much of a self-promoter, it never not any real momentum.

[@tahoh-kk4ps]

It's like that about most idea. It's not that someone who has thought of an idea first got recognized, but those whom ideas became implemented into the biggest, most influential products that got remembered.

[@bhaaratsharma6023]

While the solution is good, it's complicated and requires a lot of effort. It's not suitable for small projects or companies.

[@danieldavidezra9104]

Do u think NX could be a good solutions to the issues that was mention in the video?

[@skylvid]

Just go monorepo.

[@barefeg]

Do you even swe

[@herp_derpingson]

This is why vendoring is so important. node_modules all the way!