> […] whereas the other licenses are susceptible to being consumed and extended. Often in practice people found that does not work with BSD/MIT-like licenses:

> […] whereas the other licenses are susceptible to being consumed and extended. Often in practice people found that does not work with BSD/MIT-like licenses: you keep your changes and patches in-house and the original project moves forward. You then have to keep carrying forward your work, and you're either losing out on public fixes or have to expand energy to fix merge conflicts. Lots of vendors learned this the hard way with (e.g.) FreeBSD: you want to follow the development branch (-HEAD) and merge early and merge often. An exception to this would be one-shot forks, like Sony did with the PlayStations: you have your base functionality and it will never change for the life of the product so you don't really need future updates.