I did benchmark it against nginx and found Caddy to be 5-7x times slower, but like all benchmarks go...results are subject to ones requirements (or mistakes).
What got me away from using it:
- the directives feel intuitive but as soon as I needed a complex config it all became a chain of very implicit strings
- the caddy author(s) decided few years ago to add custom http header with their sponsors[0]. That header could not be removed, it's no longer present in current Caddy but the bad taste still remains.
What got me away from using it:
- the directives feel intuitive but as soon as I needed a complex config it all became a chain of very implicit strings
- the caddy author(s) decided few years ago to add custom http header with their sponsors[0]. That header could not be removed, it's no longer present in current Caddy but the bad taste still remains.
[0] https://news.ycombinator.com/item?id=15238315