Havoc Pennington

the docs for load(String) explain the likely issue - load does the resolve already before you add the fallback. You could use parse instead, or could use load(Config).

Hi Andrey, I can't answer the legalities of the project name question, that will be up to Lightbend. To be clear, I have not been affiliated with Lightbend since many...

maybe ConfigResolver can help? Otherwise the unfinished ConfigDocument api would be the needed thing to use the library as a parser.

The problem is that we don't have a logger... only System.err.println. There would be no way to silence spam on stderr, so to date we've avoided ever printing anything. What...

The problem is that we have a "no dependencies" policy so far for config. I guess java.util.logging isn't a dependency, but using it may well annoy people... does anyone use...

"No dependencies" is essentially a requirement from the Akka team, though it makes sense - the idea is to avoid locking people to a certain version of some other library,...

The rationale is that the file may not be a config file?

Without carefully re-reading the spec and code, my first impression is that I agree with you, I would expect an exception in these cases.

only objects auto-merge. to concat lists or strings you need to put in a substitution like `${mylist.records} [ “concat this value” ]`

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...