>That was mostly feature expansion. I meant improvement of existing workflows For desktop app developers? There were a lot of API refinements and enhancements

>That was mostly feature expansion. I meant improvement of existing workflows For desktop app developers? There were a lot of API refinements and enhancements to the widgets too, I didn't mention them all because there's far too many. >4000 files and 1.6 million lines of systemd C Just FYI these figures are incorrect, you're likely including the tests, documentation and data files. Running cloc on the current systemd code base I get around 2100 .c and .h files and 520,000 lines of C. That also includes all the other components too, not just the service manager. The service manager is a small fraction of that, it's only around 150 files including the headers. >There is an obvious cost/benefit factor here. From the perspective of a distribution I think it's much more cost effective for them to fix this once in C. To you what looks like just 30 shell scripts can quickly multiply into the thousands when you have to consider this is across all users of that distribution who might all have the same buggy set of 30 shell scripts but with different ad-hoc fixes applied. >If systemd fixed just init and basic service management in correct and minimalistic way, maybe fixing its C code here and there by power users would be rational. I think if you actually look at it, you'll find this is already what it does. That's what I saw when I actually took a few hours to familiarize myself with the code.