falkTX
commented
2 years ago Deprecation does not mean removal, only that no efforts are being put into it and developers should stop using it. There are many deprecated APIs in JACK from 10 years ago, those were never removed.
Please show me someone interested on doing session management on Windows.
And no, besides the current implementations of NSM being oriented for Unix like systems, there is nothing on it that inherently prohibits being used on some other systems. We would have to define how to find programs for macOS and Windows, but that is alike Linux tools shipping with a desktop file specifying NSM support.
Here is accepted request to deprecate jacksession: https://github.com/jackaudio/jack2/issues/389
I would argue that deprecation is a too drastic move.
In the request for deprecation it has been argued that jacksession should be deprecated, because it's has no active projects that supports it and that for most projects NSM is the better choice. But this also means, that there is actually no reason to deprecate it, because there is no actual problem here. Developers already support NSM instead of jacksession (with good reasons on Unix/Linux).
For some developers, jacksession could be a better option, because might be simpler to implement for them. The major advantage of jacksession, is that it also works on Windows, while NSM is Unix only AFAIK. Deprecating jacksession, removes this feature for session management on Windows.
So I think deprecating is too drastic.There are other ways to tell developers that it's recommended to implement NSM support on Linux/ Unix instead. This can be done, with a note in the source code and in the documentation.