Originally posted by k1e0x
View Post
Which is why applications and thus libraries are often available in a cross-system fashion either from the get-go or after some minor patches.
The problems start when development of system tools is concerned, as these require system specific code paths or using some already existing adapter technology.
Traditionally these tools were stand-alone and thus easy to switch between, but there is user demand to have certain facilities integrated into the desktop shells, e.g. network/wifi/vpn management.
Unfortunately the cross section of BSD developers and desktop developers is not very large, so there is not enough input from the BSD side during "standardization" of service APIs.
For example most interaction between desktop shells or tools and the system happens via standard mechanism such as D-Bus, so it should theoretically be possible to implement fully BSD specific system services for each interface being used by the desktop layer, but if creation of said interfaces lacks input BSD input, they might contain Linux specific bits or assume Linux specific behavior.
Cheers,
_
Comment