Hacker News Reader

>Same goes for companies. Nobody cares about you as long as everything is working smoothly, but as soon as they encounter a problem, guess who comes knocking on my door?

Companies do not use libraries, devs do. Dev ability to pay for the libs is essentially zero, and even if you try to escalate it to management and purchase the license, this can easily take a year of few to approve.

View on HN

Depends on the company. I know a lot of regulated companies that will happily pay for libs if it means they can "offload" the maintenance of them on whatever regulatory questionnaire they're filling out. For these companies, every dependency is either something they have to maintain or have a contractual relationship with the maintainer.

But if you plan on making a library for corporations to use, make the license clearly defined and don't use AGPL (it's like the legal form of hazardous materials to most corporations).

I couldn't find a LICENSE file or other notice on the repo this author was referencing.

Reply on news.ycombinator.com