As an enthusiast, my time is valuable and I want to spend it on areas of technology that interest me. NginX and Apache don’t feature on the radar. I don’t use Caddy 2 JSON. Everything I need Caddy to do I can achieve using just the Caddyfile. In just a few lines of code I have a reverse proxy or a file server or a web server all with TLS encryption. I almost feel clever! When I compare this with the convoluted, lengthy and hard-to-digest code I see for more traditional approaches, I always feel like I’ve made the right decision with Caddy. I often see threads on other forums where experienced users of traditional web server approaches say ‘I can’t seem to get system X working with the proxy/web server capabilities of Y or Z’. I think to myself ‘Really? I’ve got it working with Caddy. Don’t know what all the fuss and bother is about?’.
Plus the Caddy team on this forum are always ready to lend a hand, even with troglodytes like me. It’s one of the friendliest forums I participate in that still treat mere mortals like myself with respect.
For my needs, Caddy marginalises what traditional big players have done and puts otherwise complex subject matter within reach of the masses.