On 19 Apr 2018, at 12:09, Graham Leggett <minf...@sharp.fm> wrote: > On 18 Apr 2018, at 10:46 PM, Mark Blackman <m...@exonetric.com> wrote: > >> Is most popular the right thing to aim for? I would advise continuing to >> trade on Apache’s current strengths (versatility and documentation for me >> and relative stability) and let the chips fall where they may. It’s an open >> source project with a massive first-mover advantage and no investors to >> please. Just do the right thing, stay visible and the rest will sort itself >> out. > > I agree strongly with this. I took a look at nginx and gave it a fair > evaluation, then I discovered this: > .. > "Anything else may possibly cause unpredictable behaviour, including > potential SIGSEGV.” > > Both this document and the idea that SIGSEGV would remain unfixed would never > fly at Apache. Nginx suffers the problem in that product managers have to > trade off the pressure of new features for the marketing people over the need > to fix problems they already have. This isn’t sustainable for them. .. > The strength of httpd is that it is a tank - it just keeps going and going. > You can deploy it and completely forget about it, it just works. This frees > up our users to focus their attention on doing whatever it is they want to do.
Large crude oil tankers and formula 1 racing cars are both things that can go from A to B. Yet they have different qualities. Perhaps we need to emphasise this a bit more - that there is room for different things in this market. I’ve found the same in production - nginx can be wonderfully fast in certain settings - but can also be a relatively fragile and finicky beast best ran in serious loadbalancing/failover. Dw.
