3 ms·
The MIT-2 License: Like the MIT license but you must put 2 instances somewhere in your attribution. It is per-license, so the whoever includes your work in the
by armchairhacker 5y ago
The MIT-2 License:
Like the MIT license but you must put 2 instances somewhere in your attribution. It is per-license, so the whoever includes your work in their own project must put 4 instances, and so on.
- paxys 5y agoHow quickly would the count of MIT-2 license files in your node_modules folder exceed the number of atoms in the universe?
- sgc 5y agoIf your server crashes counting the MIT-2 license files, do they satisfy the requirements?
- idealmedtech 5y agoApproximately 240 sub licenses deep (2^3 ~ 10, 10^80 atoms in observable universe)
- paxys 5y agoThat's only for the case where project A depends on project B which depends on project C which depends on project D...240 projects deep. But what if each of them has more than 1 dependency? Also you'd have to sum up the entire series, since the licenses at every level are included in the folder, not just the top-level one.
- idealmedtech 5y ago~~Yes, in my head I was considering all of those to be, in their total, the "sublicenses." Should have been better worded; but a total of 240 distinct MIT licensed dependencies in a project is the number at which MIT-2 would run out of atoms to print on.~~ Nevermind, I see your point! In reality it would be something relating to N sums of 2^k, k being highest depth dependency for each of the N projects. Obviously we're talking bounds and not exact calculations here.
- 0des 5y agoGentlemans agreement not to tell the node guys.
- CSSer 5y agoThis does kind of get me thinking: why do we need to include full copies of licenses in distributions anyway? Couldn’t we just include the name of the license and relevant details?