21 ms·
> If you are not writing anything performance sensitive, you shouldn't be using C in the first place. Then why are all of the IO-bound low level pieces of Linu
by pizlonator 1y ago
> If you are not writing anything performance sensitive, you shouldn't be using C in the first place.
Then why are all of the IO-bound low level pieces of Linux userland written in C?
Take just one example: udevd. I have a Fil-C version. There is zero observable difference in performance.
- cardanome 1y agoudevd might actually be a good use for Fil-C. Good point. My fear is that the performance difference might add up once use it on more and more part. I imagine it uses a lot more memory. Plus once Fil-C gets adopted in the mainstream it might lower the need for devs to actually fix the code and they might start just relying on Fil-C. To be fair, systemd itself is corporate shite to begin with and I wouldn't mind seeing it being replaced with something written in a language with memory safety.
- kardos 1y ago> it might lower the need for devs to actually fix the code and they might start just relying on Fil-C. Well, the program would still halt upon memory flaw, so there would still be a need to fix it
- pizlonator 1y ago> My fear is that the performance difference might add up once use it on more and more part If that argument is valid, then why hasn't it stopped adoption of slow languages? Like, Python is waaay slower than Fil-C. And so much of Linux userland is written in shell, which is slower still.