3 ms·
No, Upstart’s design was so bad that even Scott James Remnant (the creator of Upstart) admitted it’s design was inherently flawed. The biggest problem with Ups
by cbmuser 5y ago
No, Upstart’s design was so bad that even Scott James Remnant (the creator of Upstart) admitted it’s design was inherently flawed.
The biggest problem with Upstart was that it put the dependency chain upside down and just started a service whenever it’s dependencies were fulfilled, no matter whether it actually made sense to start the service.
- ahartmetz 5y agoI remember reading about it and thought it seemed wrong, but presumably the author did his research and knew what he was doing. Oh well. His attitude and the readability of Upstart code were very good, though. The Upstart design was probably easier to implement. With the systemd design, the dependency tree needs to be traversed bottom up (figure out what needs to be started to start the targeted set of services), then top down (start dependees when dependencies are ready). With Upstart, top down was enough. Or so it seems.
- CameronNemo 5y agoDo you have a source on SJR stating that the event based design was inherently flawed?
- zxzax 5y agoI think the comments towards the bottom of this thread is what is being referred to: https://web.archive.org/web/20140928104327if_/https://plus.google.com/+KaySievers/posts/C3chC26khpq https://web.archive.org/web/20140928104327if_/https://plus.g...