Huh. I'm glad to see I'm not the only one who feels the way i feel about package management in Haiku. I argued against Linux-izing Haiku the moment package management was proposed. I fought it with words, but, since I was nobody in terms of Haiku's leadership (everyone i was tight with had left, and with them, the unified vision), no one listened to me. It's just the usual *nix-minded, open sores, "the way it's always been done", and "the way everyone else does it" mentality.
Haiku was supposed to be a BeOS clone. It has failed to live up to that goal. The user-responsiveness isn't like BeOS (the whole reason i loved it, the kernel timer was wonderfully fine grained), the net_server is no longer the net_server and instead is some monolithic kernel component, and software management has been taken from the user and turned into a package management nightmare of libs and dependencies... We shouldn't even HAVE external shared libraries anymore. The whole point of them is moot.
I gave up on Haiku when it stopped being a BeOS clone. I stop back here every few months to see what has changed and, as usual, nothing much has happened except more package management stuff. What made BeOS special isn't here, so why would the people who really cared about BeOS stick around? Are any of the developers from the original Haiku project? You know, from back in the days when it was called OpenBeOS and before it was renamed at WalterCon...? Anyone here actually attend WalterCon or is it just me?