Re:Hobby Project: A dynamic C (Hot reloading) module-based W...
by warothia on Sunday November 17, 2024 @02:54PM
(#42166611)
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
[ Parent
| on HN ]
Re:Hobby Project: A dynamic C (Hot reloading) module-based W...
by mst on Monday November 18, 2024 @04:05AM
(#42170880)
"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.
Re:Hobby Project: A dynamic C (Hot reloading) module-based W...
by kaba0 on Monday November 18, 2024 @05:56AM
(#42171335)
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.
Re:Hobby Project: A dynamic C (Hot reloading) module-based W...
by warothia on Monday November 18, 2024 @06:41AM
(#42171572)
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.