binctr does not require any runtime component other than a modern linux kernel with unprivileged usernamespace support.
Targetting OSX / Windows does make warp distinct from what I mentioned, though I don't use those OSs so I admit I didn't think about that possible issue.
Anyway, I thought this was a solved problem on both Windows and OSX since they both have conventions for self-contained applications, while linux does not.
Anyway, I thought this was a solved problem on both Windows and OSX since they both have conventions for self-contained applications, while linux does not.
This is mistaken for Windows. Even if programs are run from Program Files, they will often source their DLLs from other locations.
binctr does not require any runtime component other than a modern linux kernel with unprivileged usernamespace support.
Targetting OSX / Windows does make warp distinct from what I mentioned, though I don't use those OSs so I admit I didn't think about that possible issue.
Anyway, I thought this was a solved problem on both Windows and OSX since they both have conventions for self-contained applications, while linux does not.