This is why I like how various newer languages such as Go (golang) and V (vlang) or prototype languages like JavaScript or Lua have approached OOP. V even allo

This is why I like how various newer languages such as Go (golang) and V (vlang) or prototype languages like JavaScript or Lua have approached OOP. V even allows to easily choose if you want it on the stack or heap. With these languages, there is either no class-based OOP or classes are optional. "Freedom of choice", is way more obvious. Maybe a "shout-out" for Object Pascal in this regard too, as they have advanced records (structs with methods) and Free Pascal has simpler objects (but Delphi's dialect doesn't). Though I will say, Object Pascal's implementation of class-based OOP is a gentler version, versus the "harsher" implementations in other languages. Still, as with all the class-based OOP languages that I've seen, you are going to get forced feeding and forced to use plenty of OOP libraries. Forcing or pushing class-based OOP is debatably how things can more easily and unnecessarily go bananas. Complexity traded for simplicity. Users are usually trapped in the paradigm, until they like it (programming version of Stockholm syndrome?), and are often scared to go outside of it or think the world might end if they do.