What to obsolete before v1.5

[Horusiath]

Because we want to release v1.2 soon, it would be good to think about things we could possibly remove from v1.5. This way we give people enough time to acknowlege incoming changes. I know each person on @akkadotnet/core team has probably it's own propositions on what should we get rid of, so we can disscuss about it here.

Some of my ideas:

• Obsolete TypedActor (it's bad, most of the people who actually want to use it think about something closer to this in shape).
• Obsolete ActorProducerPipelineResolver - it's a flawed implementation, that probably noone is actually using.
• Possibly also obsolete at least some parts of the ActorProducer itself - in general the pipeline of building an actors is really complicated in current akka implementation and it makes things such as Dependency Injection hard to implement. As we need to provide some alternative to this, this may be obsoleted later.

I will probably find some more parts. Any other ideas?

[alexvaluyskiy]

I think this one should be obsoleted before 1.2 #2553

[alexvaluyskiy]

PersistentView should be removed in 1.5 (deprecated in Scala Akka 2.5)

[Horusiath]

Agree on PersistentView, but first we should provide some form of support for persistent queries for the plugins we have under our control.

[Danthar]

Took a quick look at the ActorProducerPipelineResolver. Am I correct in stating it allows you to apply a decorator like pattern to your actor ?

[alexvaluyskiy]

@Horusiath We could also deprecate Actor DSL https://github.com/akkadotnet/akka.net/blob/dev/src/core/Akka/Actor/Dsl/Act.cs

It is an interesting idea to have this DSL, but should it be a part of the core library?

[Aaronontheweb]

@alexvaluyskiy nah, keep it. It's not doing any harm by staying there and it does get used.

[Aaronontheweb]

In general, don't deprecate things because we can. Deprecate them because they are either broken abstractions or they've been / will be replaced with something better.