3 ms·

not that familiar with java, but in .net when you do this, it is very common for the implementation to be in a separate assembly, part of a different project

• cweld510 1y ago
  Doesn’t that imply an interface is necessary though, so you can compile (and potentially release) the components separately? I don’t use .net but this sounds quite similar to pulling things into separate crates in Rust or different compilation units in C, which is frequently good practice.
  • mystifyingpoi 1y ago
    Definitely that could imply the necessity of an interface, but often it's simply done, because everyone working in a project blindly follows an already established poor convention.
    • vrighter 1y ago
      by "it's common in the .Net world" I mean that it seems to be an antipattern that's blindly followed. If there's only ever one implementation, it is the interface, imo