5 ms·
I like it too. I think systemd has the misfortune/honor of touching decades-old subsystem interfaces. Any time anyone ever makes a change to something that's
by wyldfire 11y ago
I like it too.
I think systemd has the misfortune/honor of touching decades-old subsystem interfaces. Any time anyone ever makes a change to something that's worked the same forever faces criticism. systemd's feature set is so attractive that it's getting/gotten adopted by the vast majority share of linux distros. The folks who didn't prefer it but thought that they could ignore it may have been surprised and vocal when it showed up in their favorite distro.
>undocumented 200+ line init scripts ... undocumented shell scripts
Maybe we've just traded those for undocumented C init programs?
- mateuszf 11y agoEven if it's undocumented (as far as I know it is well documented), at least this code is in one place.
- simoncion 11y agoA few people have attempted to use the systemd documentation to create a reimplementation. Bearing in mind that the task is complex and largely thankless, all the folks making attempts that I've heard about have reported that the available documentation does not provide enough information to complete such a task. Note: I KNOW that documentation is seriously hard. But, one of the rebuttals of the "Systemd is complex and monolithic" assertion is "Systemd is fully documented, so you can replace any part of it with one that you've authored.". You can't honestly make that rebuttal if the state of your documentation doesn't support your claim.
- mateuszf 11y agoThat's because if the code is over some quality level (which can be measured with bugs count) then the source itself is implementation documentation. And systemd contains the more classic documentation of its behaviour for its end users.
- simoncion 11y ago> ...if the code is over some quality level (which can be measured with bugs count) then the source itself is implementation documentation. Oh, you summer child. In any complex software project, there's always a difference between the contract described by the system's specification and the contract described by the software as implemented. The big difference between the explicit contract of the documentation and implicit contract of the code is that -in areas on which the documentation is silent- the contract described by the code is subject to change at any time, without warning. Raymond Chen [0] has spilled much ink over customers who have gotten badly burned by changes in the implicit contract some time after they made use of something that the code permitted, but the documentation did not describe as possible and/or supported. [0] Microsoft most notable backwards-compatibility guru
- mateuszf 11y ago> In any complex software project, there's always a difference between the contract described by the system's specification and the contract described by the software as implemented. That's exactly the reason why source itself is better than implementation documentation - because it is always "current".
- simoncion 11y agoYou managed to miss the larger point. Perhaps these resources will be helpful. http://thecodelesscode.com/case/16 http://thecodelesscode.com/case/16 http://thecodelesscode.com/case/69 http://thecodelesscode.com/case/69
- mateuszf 11y agoIn the second story: The scribe showed that source code may be too detailed, but at the same time he showed that past view of the system will not accurate now if not updated constantly. Which is the point I'm making.
- mateuszf 11y ago