The moment that the "can also parse akka HOCON prefix compat"-feature gets introduced things can turn rapidly sour though.
Having both in a single JVM/Classloader tree structure is doubtedly part of any future ideal, but I a straight line towards that ideal could be wishful thinking. Yet, I have sort of set my mind to doing exactly that 🤭 (so avoiding the duo) On Wed, Feb 15, 2023 at 3:33 PM Matthew Benedict de Detrich <[email protected]> wrote: > Akka already has checks to make sure users don't mix and match > different artifacts on the class path. There is undergoing work in Pekko to > remove/fix these checks (i.e. see > https://github.com/apache/incubator-pekko/pull/189) however it does bring > a > general point about whether we should check if there are any Akka artifacts > on the classpath for users running Pekko and produce warnings in such a > case. > > I would predict that generally speaking if you are mixing Pekko and Akka > artifacts then this is likely a mistake and you are doing something wrong > even though technically speaking with all of the class/package/conf changes > there shouldn't be any conflicts (basically both ecosystems would sit in > their own silos). > > Thoughts? > -- > > Matthew de Detrich > > *Aiven Deutschland GmbH* > > Immanuelkirchstraße 26, 10405 Berlin > > Amtsgericht Charlottenburg, HRB 209739 B > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > *m:* +491603708037 > > *w:* aiven.io *e:* [email protected] >
