Yes I read it and it calls it a fallacy. Which is not, it’s a trade off. We could argue about how many developers actually know the implications (which would b

Yes I read it and it calls it a fallacy. Which is not, it’s a trade off. We could argue about how many developers actually know the implications (which would be a great survey to do), but I believe having this trade off by default has been the right choice for npm/Yarn. Also we need to distinct devs from lead devs, who are the owners of such responsabilities in teams.