Thanks OopsFly for this very inspring, honest, mindful and knowledge based post!
I've forgot to even think (and talk) about these points.
One useless anecdote of my life first. Sytrus was always one of my favourite synths and it kept crashing under certain circumstances. I debugged around and found out that actually something in JUCE crashed. Image-Line used JUCE for some sort of preset management. Anyways, in the end, what was to find out, was that Sytrus set the x86 floating point register at precision to 53 bit or something. JUCE had a float->int conversion hack in it that expected this not to have happened. I mailed the JUCE author that thing, and actually, in the end - also looking at many callback mechanisms - I can say, I want to play safe and "plain, easy" more than JUCE does. I think I should probably get to know JUCE more, I've no idea what it has included now. But to be honest, it didn't meet my felt standard to 100%, more like 99% or a bit below.
Type: Open source
License: even more free than GPL, even more free than MIT, a license with a lot good will and very compatible. But to be honest, the most important thing is imo, I'll never in my life try to break any rule or license, and at the same I'll never engage in a court action or anything because my own rights could have been violated. I'm a pacifist guy with ideals who wants to make music. Though, I think, GPL can limit certain peoples freedom to motivate themselfes, so it may be not the best option, but the mind fullness and community-driven aspect of GPL is still great. There is a good chance that at first above all my own code lines I would write "public domain, do what you want with it" or something better in that sense.
Platforms: The best available combination, e.g. the most used, but also the best to develop. The point is, Windows is used more, but to get a good code base - even though there is virtually no good Swift compiler for Windows yet - Swift seems so ideal. I don't want the shared_ptr boilerplate code and friends later pointing out what pointers actually could be unique_ptrs and the header boiler plate. Even though I can handle it, I think it's a bit wrong to encourage others to use C++ when real alternatives exist. EDIT: No mobile, a desktop is something that I need for music in my case.
Development-type, team-work: actually I've currently got an idea about a mind-map-driven visual development tool (maybe browser based) to have a good foundation how to get collaborative, very easy way to get a collaborated sound software. Or I just should learn GIT, because Linus Torvalds has created it and it's so wide-spread.
Money: forget about money. EDIT: Ok, I think that I buy my computer, so buying something like Intel Performance Primitives, or even licensing a sound "stretching" library like zplane(?), dirac(?), isn't completely ruled out, but honestly I'm not only quite poor, I've also adapted to a life on basics, and with Renoise in mind, I actually feel very good without zplane, dirac, melodyne, mp3. Maybe I should admit that I make my way around wanting these in the first place. Still, Renoise actually didn't add much more than mpReverb, I think. Maybe the convoluter or so? Keep me informed, please If nothing like plugin-support could add good enough DSP to
my the project, I think accepting a full GPLed project as best freedom choice as of today might be the best option.
Nature: A very solid "tower", loose kinds of dependencies, though, I think that monoglot development is better than thinking about FFIs and "to what side goes that code". That is why I ruled out the language-combinations, and I'll also go on hating Lua in Renoise. I know about the polyglot approaches, I think that it's actually mostly things which don't fit together. Still thinking about C++ and Swift.
Have to think about your post more later. Again thanks.
Edited by Mark2, 27 September 2017 - 23:23.