On Sun, Jul 22, 2012 at 5:31 AM, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> NS port is ugly, and has problems with C-g, font rendering, modifier keys,
> multiprocessing, networking.
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 patches.
First, I think someone needs to step up to the plate and prove the allegations. There have been a few of us, at least, who have spoken up that these behaviors do not occur for us. So I'm guessing the problem lies in how the binary is built and/or tested.
That said, should there be a real problem with the ns port, or a valuable feature inherent to the mac port, I will be glad to apply effort where needed.
I also think you are giving short shrift to the ageless problem of engineers finding it distasteful to work on an existing body of code. This is what I conclude happened with Yamamoto wrt the ns port. And if you were to argue that what one engineer finds distasteful, another might find elegant ... I would rest your case. :-)
-pmr