I could say speed, but the main reason for me is because it is fun. And I like to see what I can make C do. :D

"Because I can" remains an entirely legitimate reason for a hobby project.

If anything, you've gone further along the "also (at least sort of) practical" scale than I expected.

Given as mentioned elsewhere a per-request arena + bump allocator system, it might actually be -genuinely- practical (to the extent that writing application logic in C is at all ;)

Bravo.

	▲	warothia 10 months ago \| parent [-]
		Thanks! Yes, an arena allocator for each request is on my todo list. Just didn’t get to implementing it yet. :D

▲

kaba0 10 months ago | parent | prev [-]

The second point is absolutely fair and your project is very cool and impressive, but the speed one is misleading. I am fairly sure you actually leave a fair bit of performance on the table simply by how convoluted parallelism and async IO are in C, and something like Java might easily outperform it in standard CRUD backend use cases.

	▲	warothia 10 months ago \| parent [-]
		You’re absolutely right, I have not tried very hard to optimize for speed either yet. To comment was more directed at the fact most just say that “speed” is the main reason to use C, but for me it’s almost exclusively for the fun and “cool” factor.