This is a valid point. The culture of various languages forces their favorite paradigm. In the case of many class-based OOP languages (or those that have stro

This is a valid point. The culture of various languages forces their favorite paradigm. In the case of many class-based OOP languages (or those that have strongly adopted it), programmers can be publicly shamed and ridiculed for not writing class-based OOP libraries and programs. Even just using simpler objects can be frowned upon because its not using classes, even if it can be considered valid OOP too. This is why, unless forced or pressured to on a professional level, prefer dabbling in those languages where there is no classes or its truly an option, and not the main (forced) paradigm. Prefer less stress, hidden spaghetti code (pretending it's not), bullying, or shaming. Just way more enjoyable to write in languages where the paradigm that you choose is because it makes sense to solve the problem, not because "that's just what we do around here".