4 ms·
That might be quite a blocker for closed-source commercial apps that are distributed to the user. On the other hand in-house apps and web apps usually don't suf
by blablabla123 6y ago
That might be quite a blocker for closed-source commercial apps that are distributed to the user. On the other hand in-house apps and web apps usually don't suffer this problem from what I've seen. Most of the time open source libraries are strongly preferred and even if not, the closed sourced licenses for dependencies can easily be obtained by the intended user oftentimes. (At least frontend dependencies need to be MIT or BSD licensed anyway)
- tjalfi 6y agoYMMV, but most of our in-house applications use a few of the Aspose .NET libraries. Many of them are written to interact with our billing and document management systems (primitive VCS). I have written a few applications and most of them would be useless outside of our environment. I have released some PowerShell scripts to an industry specific forum, though. The biggest barrier to releasing our applications as open source are organizational. It would take a number of approvals to do so and our developers would have to review the code first. We have a small development team with a large backlog of work; it’s hard to argue that they should spend time to do this instead of a higher priority task.