dependency

Choosing a dependency

Fun fact, I thought I had already written this post, but when I wanted to reference it, I found out that I didn’t. In this post, I’d like to describe my approach when choosing a dependency. I’ll first define what I mean by dependency in the context of this post. Then, I’ll list a grid of several criteria to analyze possible dependencies with. What is a dependency?

Development

Comparing transitive dependency version resolution in Rust and Java

You learn by comparing to what you already know. I was recently bitten by assuming Rust worked as Java regarding transitive dependency version resolution. In this post, I want to compare the two. Dependencies, transitivity, and version resolution Before diving into the specifics of each stack, let’s describe the domain and the problems that come with it. When developing any project above Hello World level, chances are you’ll face problems that others have faced before.

Java

Guava is an heavyweight library and I would like this to change

Google Guava is an useful library that offers many different but unrelated features: For my Vaadin projects, I like using Event Bus to promote loose coupling along my componentsGuava offers Functional oriented collections handlingThere’s a lightweight Cache implementationetc. However, this article is not about those features but about offering a single heavyweight Uber JAR for all.

Java

Simplest Java decoupling without 3rd party frameworks

[…] coupling (or dependency) is the degree to which each program module relies on each one of the other modules. — Wikipedia http://en.wikipedia.org/wiki/Coupling_(computer_science) In object-oriented programming, removing dependencies is done by using interface. Thus, if class A is dependent on class B, we introduce interface C, which is implemented by B. Now A depends on C (see below). This first step in decoupling is called programming by interface.