> Maybe your problem is CPU-bound. Maybe you have latency limits you need to work within.
Unless you have lots and lots of time to spend micro-optimizing everything, you'll get better performance writing in Haskell.
> Maybe there are good C libraries that solve your problem
Maybe, but most of the original post is about how lacking the library ecosystem is. I can well believe that you might have some useful domain-specific libraries for the backend, but that calls for writing a backend service in C (and using something like thrift to call it), not "web programming in C".
> Maybe you just want to learn C better.
If you try and learn on a fake problem you'll pervert your learning. Web development is not amenable to idiomatic C (Cello is a good example - it's not appropriate to the sort of problems C is appropriate for, and if you learn C based on using Cello it will not make you a good C programmer).
Unless you have lots and lots of time to spend micro-optimizing everything, you'll get better performance writing in Haskell.
> Maybe there are good C libraries that solve your problem
Maybe, but most of the original post is about how lacking the library ecosystem is. I can well believe that you might have some useful domain-specific libraries for the backend, but that calls for writing a backend service in C (and using something like thrift to call it), not "web programming in C".
> Maybe you just want to learn C better.
If you try and learn on a fake problem you'll pervert your learning. Web development is not amenable to idiomatic C (Cello is a good example - it's not appropriate to the sort of problems C is appropriate for, and if you learn C based on using Cello it will not make you a good C programmer).