BCHS software stack: BSD, C, httpd, SQLite

I've spent the better part of the year messing around with every HTTP server I could get my hands on. I would not recommend OpenBSD httpd. It's supposed to be simple, and it is simple compared to Apache, but it also has way fewer eyes on it. Ultimately, a big pile of string-handling C is likely to have some problems. There was a trivial-to-exploit server-crashing segfault in httpd's FastCGI implementation that was only fixed in the last month or so…

> BCHS (pronounced /biːtʃəz/, beaches) is for real development. It's a hipster-free, open source software stack for web applications. > Why C? fewer hipsters : hipsters dislike memory managment Is this meant to be ironic? Spinning up web apps with C in 2017 seems like a supremely hipster thing to do.

Doing web development in c and getting that sweet performance boost is very tempting but the time it takes to develop even a simple website is just not worth it. I would rather spend a few pound extra on servers and goto the cinema than the hours of developer time it would take to build PHP sites in C++

I really like the idea of learning this. Using a unixy system, sqlite, and plain old CGI sounds like such a good idea to cut through the mountains on mountains of abstractions we've got today for React-based SPAs. But C is insecure. For all intents and purposes for me, a hobbyist, it is impossibly so. Security experts and C professionals the world over work hard to make things secure, yet there are (virtually) always vulnerabilities discovered (or worse, not), and…