←back to thread

Show HN: A dynamic C (Hot reloading) module-based Web Framework

(github.com)
127 points warothia | 1 comments | 17 Nov 24 18:12 UTC | HN request time: 0.251s | source
Show context
gwbas1c ◴[17 Nov 24 19:44 UTC] No.42166517[source]▶
Important question: Why would anyone develop a web application in C? Typically web applications lean heavily on garbage collection and memory safety, because their bottlenecks are very rarely CPU/memory issues. The ROI on manually managing memory just isn't there for a typical web application.
replies(10): >>42166611 #>>42166628 #>>42166883 #>>42167123 #>>42167520 #>>42167739 #>>42167933 #>>42168255 #>>42169645 #>>42173754 #
SvenL ◴[17 Nov 24 19:56 UTC] No.42166628[source]▶
On the other hand memory management in web applications is quite easy. Most of the stuff is only required for the lifetime of a request. Some stuff needs to be available the whole application life time.
replies(1): >>42168057 #
smt88 ◴[17 Nov 24 22:45 UTC] No.42168057[source]▶
You can do this with other languages (C# for example) as well. Memory is so cheap, though, that most companies should spend their money on increasing memory rather than on paying programmers to optimize memory usage.
replies(3): >>42168124 #>>42168203 #>>42168940 #
1. SvenL ◴[17 Nov 24 23:13 UTC] No.42168203[source]▶
Yes, for most use cases it doesn’t really matter which language is chosen.

Regarding just spending more money on memory - I agree that it’s definitely cheaper but it’s not only about wasting bytes of memory. If the garbage collector has a lot of work to do it may also impact response time/throughput.

And yes, C# did a pretty good job with implementing mechanisms for reducing allocations on a language level. This definitely helps to reduce garbage collection.