Re: [akka-user] Akka, Akka Typed and dead code elimination

Hi Roland, > On 3 Feb 2018, at 5:56 pm, Roland Kuhn wrote: > > I agree on the tendency. In the case of Akka there are two reasons for using > reflection and neither of them is caused by a lack of static types: > extensibility and remote marshaling. A new implementation

Re: [akka-user] Akka, Akka Typed and dead code elimination

Sent from my iPhone > On 3. Feb 2018, at 07:25, Christopher Hunt wrote: > > Hi Roland, > >> On 3 Feb 2018, at 5:16 pm, Roland Kuhn wrote: >> >> could you elaborate on how exactly Akka Typed is expected to help with your >> use-case? The only

Re: [akka-user] Akka, Akka Typed and dead code elimination

Hi Roland, > On 3 Feb 2018, at 5:16 pm, Roland Kuhn wrote: > > could you elaborate on how exactly Akka Typed is expected to help with your > use-case? The only difference I can see is that the new (and currently > removed) implementation contained fewer extension points,

Re: [akka-user] Akka, Akka Typed and dead code elimination

Hi Christopher, could you elaborate on how exactly Akka Typed is expected to help with your use-case? The only difference I can see is that the new (and currently removed) implementation contained fewer extension points, but that is unrelated to whether ActorRef has a type parameter or not.

Re: [akka-user] Akka, Akka Typed and dead code elimination

Really Christopher… we’re not heavy on reflection, check other libraries in the Java ecosystem ;-) The single reflection things we have is classOf style actor creation, and initial startup things, that’s it. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend

Re: [akka-user] Akka, Akka Typed and dead code elimination

Thanks for the reply Konrad. Although my use-case is somewhat forced by working with constrained device memory and enterprise security, I think that there’s a broader concern. My understanding is that the JVM is embracing ahead of time compilation and the potential for dead code elimination

Re: [akka-user] Akka, Akka Typed and dead code elimination

Hi Christopher, I’ve worked in the past on an Scala on Android project, so have had the “pleasure” of battling proguard for similar reasons. In general I guess the “core stuff” needs to be kept, which would mostly be the akka.actor and dungeon things. AFAIR proguard is ale to understand

[akka-user] Akka, Akka Typed and dead code elimination

Hi everyone, I’ve got a requirement to run services on machines with limited resources, memory in particular, but also disk (disk == memory for my use case!) In addition, I wish to reduce the attack surface area of a service by eliminating code that isn’t used. I’d therefore like to take a