> Furthermore systemd seems to be rewritting so many things so fast that we are losing hard won lessons from our history.
Actually you got this one backwards ... a rewrite does not lose you any "hard won lessons from history" but it allows you to not repeat mistakes made in the past (i.e the opposite).
Posted Apr 26, 2012 7:41 UTC (Thu) by ersi (subscriber, #64521)
[Link]
Well, I'd say you're both right.
It's all about the frame of mind when rewriting whatever code we're referencing to.
If you're rewriting to just throw out the past, you're in my opinion likely to not care what the current code does in detail. Which likely ends up with "new" history lessons coming - when you need to iterate over this rewrite and fix stuff you didn't think about.
If you're rewriting a section/whole program to merge/extend it, I think you're more likely to try to get a good grasp of what it does to a larger extent and keep bug fixes and quirks while baking new code and refactoring some old code.
Is systemd unix?
Posted Apr 27, 2012 22:24 UTC (Fri) by yoe (subscriber, #25743)
[Link]
Actually that's not true, for many of the reasons explained here: