Re: [Jack-Devel] The Situation(s) With JACK

On 14 Dec 2011, at 14:41, Felix Homann wrote:

> Hi,
> 
> the last couple of days I've been watching this discussion with interest and fear. The fear of loosing a great tool.
> 
> Am 14.12.2011 15:02, schrieb Stéphane Letz:
>> OK, assuming the answer to "do we gain something by doing a new
>> implementation" is yes, the next question is : who is going todo that?
>> who is going to do multi-OS support? who is going to port current
>> specific code (backend, bridges?) to this now code base? who is going
>> to debug/test it? Stephane
> 
> From an outside perspective I guess you can not set these questions apart: The ultimate possible gain of starting a new implemetation was if it would get the both of you working together on one implemetation.

I second everything you just said.

JACK has enjoyed contributions from a list of very talented, dedicated people and has become something very valuable. I agree with Paul's feelings that there are real problems with the current arrangement. If efforts can be unified I think this will be a great thing.

Of course, we seem to be left with a choice between Paul et al moving to a codebase they don't entirely agree with (and given the huge amount of effort it would be for them to do such a move, I can well understand that they would rather be moving to something they like) - or between Stéphane's group having to redo huge quantities of work they already consider finished.

If there are conceptual issues with JACK2's implementation (and it sounds as if there are) it is always tempting to consider a re-architecture. But I'm not able to even comment on how much work it would be. Will a new implementation in "proper C++" would save a lot of future effort? It might be more of an investment than a cost, particularly if it is felt that new people would be better able to get to grips with the code.

1323876944.25880_0.ltw:2,a <9EEB740F-9967-461D-8CB4-CEE74F928370 at gmail dot com>