GitHub user mdedetrich added a comment to the discussion: Replace typesafe config for sconfig for Pekko 2.0.0
> I don't think we should remove it, as Akka is still using it, sconfig is > great, but it's still a one-man part-time job. The entire scala center maintains sconfig, and it also has funding support. Typesafe config is in actuality far less maintained, otherwise I wouldn't bring this up > The only way I think we should migrate is we split all Scala implementations > into dedicated projects and then compile Pekko to Scala native and Scala Js, > otherwise, I think we should keep it as it is. None of this is necessary, pekko already requires Scala and its going to be a depenency as anything else. The API for sconfig is deliberately written to be java safe (just like our `javadsl` api's are), in fact its entirely source compatible with typesafe config. GitHub link: https://github.com/apache/pekko/discussions/2186#discussioncomment-14362040 ---- This is an automatically sent email for notifications@pekko.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@pekko.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
