What freaked me out a bit was reading “100% mission critical”. I may not fully get the niche issues that the product resolves here but if it’s really 100% mission critical, I’d only use FOSS or make a mix of tools.
What freaked me out a bit was reading “100% mission critical”. I may not fully get the niche issues that the product resolves here but if it’s really 100% mission critical, I’d only use FOSS or make a mix of tools.
The app is not activation-locked to a remote server, from what I can tell.
There is nothing stopping the author from buying a 2013 Mac Pro "Trash Can" with 64GB RAM, and running it in perpetuity. RTF import/export won't stop working, documents won't bloat beyond what 64GB RAM can handle, etc.
In many ways being able to run something on a stable, well emulated, platform can be a better way to know some tool will always be around than to have the source code for the tool itself (even if that is definitely also a good thing). There is a much better chance that someone will e.g. keep maintaining some forks of DOSBox to keep it running than that there will be people around to maintain a specific tool. Not sure how that looks for MacOS applications? Of course support for running fully offline and without messy DRM is a must.
A quick search pointed me to https://github.com/darlinghq/darling