> None of that is inherent, i.e. it can all be fixed without having to use a
> different API. So we need to someone to step up to the plate and provide
We have an existing body of code that it seems no one is excited to maintain,
and a fork that at least one person is very eager to maintain.
Is the correct answer to say that we're not moving forward until someone gains
interest in something currently unexciting? Or should we migrate to a
code-base where we have a guaranteed active developer?
Waiting until NS finds its star developer does not seem like a real strategy
to me -- unless you don't have a problem with NS currently. But this is a
genuine issue for many of us. It prevents me, personally, from following
trunk and providing fixes/bug reports relative to trunk.
Simply because non-OS X users don't seem to care what happens on OS X, doesn't
mean it should be this easy to ignore the problem. It hasn't "gone away" in a
few years now, and I don't see why that's suddenly going to change now.
Can everyone who has issues with NS please help by gathering data about your
environment and use cases? The problems I have manifest even with -Q. I
build as follows: