From what I have encountered: Akka was mostly used as Http server (akka-http). There is Http4s which can replace that and I think is great. Also its easy to use it with tagless final or zio's IO.
Actors computation model depending on use case can be replaced with message brokers or Scala libraries. Like cats-effect or zio for composable concurrency primitives and fs2/zio-streams for stream computations. I know there are actor use cases beyond that, but I am yet to encounter project these days where picking akka would be my first choice.
I have nothing against akka and I definitely enjoyed developing with it 5 years ago.
So there is Loom comig from one side, and effect libraries like cats and zio from the other side... great promises, but would I trust them with production code?... Hmmm...
But there is always the option to lean back on Java and Spring and JEE - the old and boring but tried and tested ways on the JVM.
In my humble opinion, Akka is becoming less relevant in Scala community. I don't see new projects picking it up as there are better alternatives.