> Yeah; and unlike nginx and Apache, Caddy has a higher degree of memory safety, so it's impervious to a whole class of vulnerabilities.

At the expense of the memory footprint because developed with Go. Hi Caddy creator!

> At the expense of the memory footprint because developed with Go. Hi Caddy creator!

Makes sense to me that something built in a language with more memory safety than C would use more memory, but is it really significant in practice? I use go every day and memory usage has not been a significant issue for many applications.

I don't use Caddy, but I've written plenty of Go apps (which usually implement their own HTTP server with net/http) with plenty of users, and memory usage has never been much of a concern.

There are other performance concerns of course, e.g. GC latencies, and at times the GC may bite you. See e.g. the "taming Go memory usage" story from a few days ago[1], but this usually isn't a huge concern for many use cases.

[1]: https://news.ycombinator.com/item?id=28608083

We're talking about shaving megs here rofl

cmon now

terminal systems engineer brain is everywhere

Might be nice to disclose your involvement when commenting on caddy-related threads.

> I'm the author of the Caddy web server.

I'm guessing you mean the about section of your profile. I'm just saying that it's nice to make that more visible when you have that sort of involvement in the topic and it is not obvious.

Why? I prefer when people don't flash their badge at me to support their statements. Words should stand on their own without appeals to authority.

It's more the other way around, when saying things about your own product it's nice to disclose your involvement since that definitely colors your view. Especially in cases like this where it's hyping the product.

Definitely not the right place, but thank you for creating Caddy. :)

Thanks, you're welcome!