Yet another replacement of an already established system with something completely different because one developer doesn't like the way it's designed.
Did you even read the article or are you just trolling? He tried to use NetworkManager and it turned out that it does not fit environments that consists of more than WLAN and Ethernet.
"One problem was the difficulty of extending NetworkManager to support additional kinds of connectivity; Holtmann says that significant portions of NetworkManager's code base would have to be rewritten to facilitate support for WiMAX, for instance. He faced similar challenges when he attempted to overhaul NetworkManager to enable tight Bluetooth integration. (...) ConnMan is lighter and has fewer mandatory dependencies. PolicyKit and the udev device management system are optional dependencies, meaning that ConnMan can work without them in environments where they aren't needed."
Member since:
2005-07-06
Did you even read the article or are you just trolling? He tried to use NetworkManager and it turned out that it does not fit environments that consists of more than WLAN and Ethernet.
"One problem was the difficulty of extending NetworkManager to support additional kinds of connectivity; Holtmann says that significant portions of NetworkManager's code base would have to be rewritten to facilitate support for WiMAX, for instance. He faced similar challenges when he attempted to overhaul NetworkManager to enable tight Bluetooth integration. (...) ConnMan is lighter and has fewer mandatory dependencies. PolicyKit and the udev device management system are optional dependencies, meaning that ConnMan can work without them in environments where they aren't needed."