[mholt]

What? They're not even comparable. Here are distinct advantages of all three as I see them:

- Traefik has cross-platform, highly dynamic proxying

- Apache has such widespread use and market saturation

- Caddy is the only server, even in the face of mod_md, to have fully automatic HTTPS by default

The thread you linked to has nothing to do with any of this, except that it links to this comment by myself, which preempts your claim: https://news.ycombinator.com/item?id=15433788

[throwaway0071]

They are absolutely comparable and the advantages each one have don't exclude the others from attaining the same features.

Traefik cross-platform? All others are. Highly dynamic. What does that even mean? All are "dynamic".

Apache has widespread use and market saturation... how's that the single advantage it has? It's been evolving a lot.

Caddy is the only server to have fully automatic HTTPS? How much longer mod_md get that?

I think you've missed all of my single point and kind of confirm my fears.

The link which I posted has everything to do with this discussion. It's about Caddy thinking a bad business plan will work because "caddy is the only server to have fully automatic HTTPS by default".

Last question, is Caddy thinking of hiring a CEO or sales person? I think it should.

[mholt]

> Traefik cross-platform? All others are.

Not true - (stable) mod_md builds are not yet available for all platforms.

> how's that the single advantage it has?

Where did I say it was the "single advantage"?

> Caddy is the only server to have fully automatic HTTPS? How much longer mod_md get that?

You forgot "by default" -- and probably never, not on Apache's main release tree. Or at least not for a long time.

> I think you've missed all of my single point and kind of confirm my fears.

Why are you afraid? What are you afraid of? This is literally the epitome of spreading FUD.

[throwaway0071]

> mod_md builds are not yet available for all platforms.

Do you have reason to believe they won't be? Are you betting your business on the failure of Apache to do basic release engineering?

> Where did I say it was the "single advantage"?

That's fair. Because you listed it then I think that's the "major" advantage. Is that right?

> ou forgot "by default" -- and probably never, not on Apache's main release tree. Or at least not for a long time.

Why? Let's Encrypt and HTTPS by default being something that a lot of people want, why do you think Apache will ignore that and not include mod_md in Apache "for a long time"?

Competition is good. I don't have major reasons to be afraid but I would like Caddy/Traefik and others to succeed. From the very basic mistakes they're making in coming up with a business plan, I don't think they will. And no, being open source alone is not reason enough to ensure project survival.

If you re-read your own comment, I think you're the one spreading FUD about those other projects (and their implied inability to outpace Caddy).

[Touche]

Because those projects are very conservative about making things default. Apache famously has (had now?) bad defaults that no one should use, just for compatibility reasons.

Keep in mind that caddy is not only https by default, it's HTTP/2 by default as well. How long until that is by default in Apache?

And I don't think those are even the killer features of Caddy. They are the things that drive people in, but the real killer feature is how easy it is to configure.