config
config copied to clipboard
lightbend
choose a new name (not "Typesafe Config")?
the name is now doubly inappropriate: there is no more company called Typesafe, and the library is string-centric, not type-centric
we have moved the repository from the typesafehub organization to the lightbend organization, but we might also consider pushing through a full rename, whether to "Lightbend Config" or some "HOCON"-based name, or what
How I understand the library name is as a cute pun as "type-safe config", which I understand as "way more type-safe than java properties" - if you want to getInt, and we have getDuration and other ones. I understand what you mean with it being "strings anyway" though ;)
Honestly to keep the nice pun I'd propose to make the lib lightbend / typesafe-config as a nice pun ;) WDYT?
Something to think about name-wise is that really this library has multiple things in it:
A) a Java interface (Config, ConfigObject) for using and merging configuration data B) a convention for getting a default instance of Config, without relying on some part of the application getting to run first and register anything (ConfigFactory.load and the patterns in the examples). Included in this are conventions for how to stack env vars, system props, etc. into the default instance C) the HOCON file format parser D) I guess analogous to C) but far less code, a little bit of code for converting Properties to Config
These aren't completely orthogonal, but for example it probably would be possible to factor the HOCON parser out (in the same way YAML could be as just discussed on #169 ).
Most of the ports to other languages seem to be going with some sort of HOCON-related name.
Anyway not to complicate the discussion :-) but an obvious name seems like java-hocon or something, but then that really is only about aspect C). For the whole bundle of A)-D) the point of it originally was to tie together Akka/PlayFramework conventions and syntax, so it was "config for the Typesafe stack"
"Typesafe" here afaik originally meant "Typesafe the company" not "typesafe the API property"
I'm still emotionally distraught from watching @retronym peel the "Typesafe" sticker off his laptop today.
I vote we call it typesafe-config. I think about it in the same way as @ktoso.
~I vote we call it hocon. My second choice is java-hocon.~
(edit, 2020: changed my mind)
@TimMoore makes the point that many may know this library by its maven coordinates com.typesafe:config or its package name com.typesafe.config, both things we're very unlikely to change.
So maybe it's best to:
- rename the library "Typesafe Config"; and
- rename the repo
lightbend/typesafe-config.
Say something if you feel strongly against that.
an obvious name seems like java-hocon or something, but then that really is only about aspect C). For the whole bundle of A)-D)
See also https://github.com/lightbend/config/issues/460#issuecomment-541062097 where it's more obvious why this shouldn't be called something HOCON-based.