GitHub user ptrdom added a comment to the discussion: Replace typesafe config
for sconfig for Pekko 2.0.0
In my opinion, ideally every core feature – such as config – should be internal
or depend only on ASF projects, meaning both Typesafe Config and sconfig are
problematic in that regard. So the three solutions I see are:
1) Asking for Typesafe Config or sconfig to be donated to ASF.
- @pjfanning has already suggested this in regards to sconfig,
1) Forking Typesafe Config or sconfig into ASF.
- I understand that @He-Pin is against this, but not all OSS is created
equal, and ASF is a safer organization for long term health of a project than
individual owners or most other organizations, which I feel is of particular
importance for this case.
1) My personal favorite - dropping dependency on Typesafe Config altogether and
going all in with programmatic configuration. Whether it is expansion of
`ActorSystemSetup` or some other abstraction which would be internal to this
project. Then have optional sub-projects that allow deriving this programmatic
config from some other config library available, whether it is Typesafe Config,
sconfig or whatever else there might be.
- I understand that it is way, way more effort, but it seems most
purposeful and forward-thinking, at least to me.
GitHub link:
https://github.com/apache/pekko/discussions/2186#discussioncomment-14363504
----
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
