Linked by Thom Holwerda on Mon 14th May 2012 13:55 UTC
Permalink for comment 518045
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2009-07-18
Requiring dependencies on optional components (what does the boot process have to do with a desktop?) is typically a sign of a bad software architecture.
A better design is modular so that you can add extra functionality on Linux but still keep it operational on other systems as well (either without that specific functionality or with a similar one specific to that system). Having a hard requirement is just lazy and such an attitude typically leads to code that is less stable, harder to maintain and more difficult to adapt if systemd is replaced by the next best thing.
From my own experience, keeping cross platform/compiler compatibility is a good thing even if you care about one platform only. Not just from a programming point of view, it also keeps options open for the future.
Edited 2012-05-14 15:29 UTC