3 ms·
Similarly to anything you use that is FLOSS, which could have few devs and languish, teams with bizarro changes of direction, and so on. You just get the assur
by coldtea 6y ago
Similarly to anything you use that is FLOSS, which could have few devs and languish, teams with bizarro changes of direction, and so on.
You just get the assurance that in the off chance somebody (including you) cares enough to maintain it, has the time, and is competent, they have have the license to do so.
But that's not that big a deal, except if its a project with many diverse backers and large diverse community (e.g. something like MySQL or SQLite or even Webkit will survive and be forked if needed - something like the average 1-3 main dev project not so much).
- quickthrower2 6y agoThis is a big ol thread but I think it is worth touching on software design. If an app can be a desktop app written in say JS (Java c# or similar term back-compat language) and not need “infra”. Or if it can be a Unix until that does one thing well. Then that is more likely to be a thing that can be forked and untouched for years and just work. Granted anything that interacts with web services may have bit rot. However solid principles may allow those parts of code to be surfaced out to plugins etc. Anyway let’s put it this way. I use YNAB 4 desktop budgeting software. No longer supported, not even FOSS and I’m not worried I can run that thing for the rest of my life, with little hassle, as long as I can run the last version of Windows that supports it in a VM.