3 ms·
Don't most open source licenses have some form of "we are not responsible, use at your own risk" clause? In any case, Django has provided this for years, and i
by z9znz 4y ago
Don't most open source licenses have some form of "we are not responsible, use at your own risk" clause?
In any case, Django has provided this for years, and it probably is one of the reasons why a lot of apps get built on Django. I am really not a fan of Django, so I only use theirs if I'm paid to work on it. But if they can do it, why aren't the other popular frameworks giving that common need more attention?
I would argue that it is actually a value proposition and that it is one reason why Django has some of the marketshare it has.
- azemetre 4y agoLiability can also mean dealing with all the issues in supporting and maintaining the edge cases, not just legal woes. It is probably much easier, from a maintenance standpoint, to simply allow other libraries take the mantle and just structure your project to play nice with middleware. Much easier to just say “use package x for auth support.”