prophittcorey

Don't give me any more ideas!

I meant to express the layers of abstraction feel strange to me in a typical setup.

A typical setup today looks like:

nginx -> puma/unicorn/gunicorn/etc -> your code

With cgi that middle layer is gone. It's just:

nginx -> your code

The layer reduction is nice when it comes to things like debugging. You don't have to guess if the middle server is removing a header, failing to forward a header, etc.

It's obvious who does that with cgi.

I generally like "C-style C++", but I find it difficult to draw the line between C and C++. It's too easy to keep reaching into C++ for "just one more thing."

That may be a me problem.

I didn't want to state why C and not "X" because the comments would have devolved into an all out language war.

I wanted to try my hands at a monochromatic website and chose two shades that were far enough apart to pass a AAA contrast rating for accessibility. I'll try to improve it soon.

It was 100% human slopped :)

The standard string functionality is painful. I wrote my own string view and string builder that work with fixed size strings. No memory allocations, etc.

SQLite can handle multiple concurrent requests if it's set to WAL mode. Reading is all non-blocking/concurrent but writing is still synchronous. You should also set the "busy timeout" or else your blocked writes will timeout immediately.

To be fair, the HTML and CSS in C wasn't too bad.. the Youtube scraper was also written in C and that was a lot more painful :)

Kivy led to one of my first open source contributions in 2014. I submitted Kivy file support to Vim. It was done via patch diffs over email with Bram Moolenaar. It's still in Vim today[1].

RIP Bram.

[1]: https://github.com/vim/vim/blob/master/runtime/syntax/kivy.v...

I have written quite a few things in Go.

https://github.com/prophittcorey