externalized-properties VS AssertJ

https://github.com/joel-jeremy/externalized-properties - A proxy based configuration library

P.S. I am the author of the Externalized Properties library. The primary reason I created the benchmark is to test how this library fares against the other existing configuration solutions. Just thought of sharing the results here in case others may find it useful. :)

I just released an alpha version via Maven Central. Feedback is very much appreciated! Installation instructions can be found in README: https://github.com/joeljeremy7/externalized-properties

I just released an alpha version via Maven Central. Feedback is very much appreciated! Installation instructions can be found in README: https://github.com/joeljeremy7/externalized-properties

Maybe not the feedback you want, but would you consider developing something that looks like plain old (and frankly beautiful) AssertJ?

AssertJ - fluent assertions

AssertJ https://github.com/assertj/assertj

Truth or AssertJ for easier assertions in tests with better exceptions

While we are at it: AssertJ is very powerful for writing assertions.

In OO you can make beautiful DSLs that allow really declarative use within that domain, e.g. test assertions in AssertJ, but everybody in the OO world is sensible enough to not try and claim OO as such being declarative. I guess they don't feel a need to try to prove the superiority of the paradigm.

AssertJ comes with a variety of assertions that can be chained together and are specific to the type of your "actual" variable.

At any rate it comes from a library called assertj.

While Hamcrest add some fluentidity to unit tests ä, I prefer the fluent assertions of AssertJ.