BCHS: OpenBSD, C, httpd and SQLite web stack
learnbchs.org
BCHS: OpenBSD, C, httpd and SQLite web stack
1–10 of 158 posts
Re: BCHS: OpenBSD, C, httpd and SQLite web stack
#2It seems pretty crazy to write web-facing apps in C, with no memory safety at all.
(They do have "pledge" but even in the most restricted case, this still leaves full access to database)
Re: BCHS: OpenBSD, C, httpd and SQLite web stack
#3I'd be fine with this, even totally on-board, if C weren't so awful with respect to text. You don't even have to worry too much about free()ing your malloc()s if you design around short-lived processes. But this is just asking for security concerns among the tangled web of string and input processing your bespoke C routines are likely to develop into.
Pair it with a better, more modern, and safer native-compiled language and get the same effect. Zig, Nim, Go, hell even Carp.
Re: BCHS: OpenBSD, C, httpd and SQLite web stack
#4s/C/NIM
Why don’t more folks use NIM for web development. Seems like the perfect blend of performance, ergonomics and productivity.
Re: BCHS: OpenBSD, C, httpd and SQLite web stack
#5I'd be fine with this, even totally on-board, if C weren't so awful with respect to text. You don't even have to worry too much about free()ing your malloc()s if you design around short-lived processes. But this is just asking for security concerns among the tangled web of string and input processing your bespoke C routines are likely to develop into. Pair it with a better, more modern, and safer native-compiled lang…
Same guy wrote a rad tool that will generate server code, schema, frontend using a markup language called ORT.
Will generate Rust and typescript if ya want.
Re: BCHS: OpenBSD, C, httpd and SQLite web stack
#6It seems pretty crazy to write web-facing apps in C, with no memory safety at all. (They do have "pledge" but even in the most restricted case, this still leaves full access to database)
Funny to reflect that there was a time not so long ago when writing web apps (CGI usually) in C wasn't at all unusual (shortly before Perl became much more popular for this). And today, it is indeed kind of crazy.
Re: BCHS: OpenBSD, C, httpd and SQLite web stack
#7I'd be fine with this, even totally on-board, if C weren't so awful with respect to text. You don't even have to worry too much about free()ing your malloc()s if you design around short-lived processes. But this is just asking for security concerns among the tangled web of string and input processing your bespoke C routines are likely to develop into. Pair it with a better, more modern, and safer native-compiled lang…
well there are still many large software written in C, e.g. nginx, lighttpd, even linux kernel.
I checked BCHS a few years back, the key piece is that it's Openbsd, if it's Linux it might have caught on, due to linux's popularity, good or bad. This could be useful for embedded device for example, but not so many embedded devices running OpenBSD, if any at all.
Re: BCHS: OpenBSD, C, httpd and SQLite web stack
#8I'd be fine with this, even totally on-board, if C weren't so awful with respect to text. You don't even have to worry too much about free()ing your malloc()s if you design around short-lived processes. But this is just asking for security concerns among the tangled web of string and input processing your bespoke C routines are likely to develop into. Pair it with a better, more modern, and safer native-compiled lang…
well there are still many large software written in C, e.g. nginx, lighttpd, even linux kernel. I checked BCHS a few years back, the key piece is that it's Openbsd, if it's Linux it might have caught on, due to linux's popularity, good or bad. This could be useful for embedded device for example, but not so many embedded devices running OpenBSD, if any at all.
The C library used (https://github.com/kristapsdz/kcgi) is portable and working on linux as well. Putting this behind nginx as fastcgi seems very well doable.
Re: BCHS: OpenBSD, C, httpd and SQLite web stack
#9It seems pretty crazy to write web-facing apps in C, with no memory safety at all. (They do have "pledge" but even in the most restricted case, this still leaves full access to database)
Though the majority of running web servers, load balancers, protocol proxies like php-fpm, etc, are probably written in C :)
Re: BCHS: OpenBSD, C, httpd and SQLite web stack
#10It seems pretty crazy to write web-facing apps in C, with no memory safety at all. (They do have "pledge" but even in the most restricted case, this still leaves full access to database)
Funny to reflect that there was a time not so long ago when writing web apps (CGI usually) in C wasn't at all unusual (shortly before Perl became much more popular for this). And today, it is indeed kind of crazy.
Depends on your definition of "not so long ago" - it's certainly most of the history of the web. The point when Perl, PHP, and Java started to become the dominant web app technologies is about as far from the present day as that point was from the moon landing.