The mit license allows someone (some company) to modify the open source codebase and sell the result without making their modifications public.
It allows the software equivalent of the enclosure of the commons.
If there was a particularly large or significant and widespread codebase —like for example the coreutils— that was used everywhere and mit licensed, a company could make their own slightly different coreutils without publicizing the differences and use their position in the market to enclose the commons of knowledge about the use of that software. Such a situation would lead to a fractured feature ecosystem and confusion around best practices. In that environment, the biggest and most popular software distributor would benefit because their product would be most common and therefore the best target to design around.
I know there’s a lot of “coulds” and “woulds” in that sentence, but that’s exactly what happened in the 80s and 90s with the ostensibly open source Unix codebase and the reason why the gpl was invented.
The other reply is a good answer, but also dropping a video with no context or explanation is a hallmark of content spammers and growth hackers.
Even if looking like a crappy kind of poster isn’t enough to dissuade someone from just dropping a link and fucking off, providing some context and input to how and what the link will do and what it means as a post in the particular community is a lot better behavior and starts a conversation as opposed to doing nothing.