BCHS
Now that loudmouth Linus is out of the picture probably soon.
What's the deal with *BSDfags and picking horrible fonts?
We've all been brainlets about C at one point or another, learn from your mistakes instead of being butthurt.
It's a troll.
Alright everyone, gather round. Here are the easy options for a c backend.
Nginx: with nginx-c-func, it supports aio threads/thread pooling and you can do upstream requests to avoid bogging shit down. nginx third party modules compiled in make this objectively the best choice due to support and flexibility.
github.com
Kore.io, faster than the above option but it's smaller project. secure and fucking easy to set up. lots of examples, secure, has a state machine (for long running ops) and postgres connection built in. Also supports python if you need to mix shit up.
github.com
Then there's libh2o.
This is the fastest, like, fucking fast. If my laptop actually had a nic that could support it it would saturate a 3gbps connection. ON A LAPTOP. It's fucking sexy but it's harder to set up than both of the above.
github.com
You should use the techempower benchmark example for a shortcut on getting your project up to speed.
github.com
There are others but these are the top picks. If you just want something that works then kore is your best bet. if you want ultimate ease + easy integration with a bunch of other shit plus lots of stackoverflow help then use the nginx option. If you want max speed then use h2o. I'll open source my redis/postgres/json project in a couple of weeks after I test it out.
Good luck guys. Fuck Rust/Go.
>Fuck Rust/Go
"Guys, here's what you need to cross the Atlantic on a cardboard box. Fuck the guys using barrels and bathtubs!"
so basically if you can't use grep properly?
This seems cool, but I can't justify using it when Apache and PHP just work, and are probably a lot less time. If I'm only making a personal webapp, then how does the performance benefit me?
>using libraries is unsafe
Sure thing rust shill