You can do that, actually, for your own use. You can’t distribute the result. (Freedom 0 in the FSF four freedoms.)
Yes, there are always new people who get this wrong and the only thing for it is education.
Telling people that they don’t have to learn anything about how the software licenses they use work, that it’s just a matter of opinion, is not helping.
I don’t think anyone is saying that you shouldn’t learn about the licenses you use, only that he’s taking a big-tent view of open source focused on getting more people paid to contribute to the commons so we don’t have so many projects depending on a handful of people choosing to contribute unpaid labor.
I think we should have a big-tent view of software and software licenses. There are good reasons to use a non-open source license. If you want to block Amazon from running your code on their servers, an open source license is not for you, and you should choose something else. There are other licenses that make source code available under more restrictive terms.
The fact that there's a clear definition for what an open source license is, and some licenses meet it and others don't, means I can make a statement like that, talking about a bunch of licenses as a group.
If it just means "licenses that make source available with whatever terms" then it's a less useful way of classifying and discussing licenses.
Most terms in the English language are fuzzy that way, but this one has a clear definition and I would like to stick with it.
Yes, there are always new people who get this wrong and the only thing for it is education.
Telling people that they don’t have to learn anything about how the software licenses they use work, that it’s just a matter of opinion, is not helping.