Of course, but OOP is typically about putting methods on classes, inheritance of behaviour etc.
JS Objects aren’t typically used that way, they tend to be used as pure data containers. At least, that’s how we mostly use them.
Occasionally, we’ll use objects to simplify passing multiple arguments including arrow functions, but I’d say that doesn’t really count unless the arrow function mutates the object it’s a part of.
Of course, but OOP is typically about putting methods on classes, inheritance of behaviour etc.
You’re referring to one subtype of OOP. That may be what most people mean when they say OOP, but that doesn’t make it correct. Object-oriented programming is programming with objects, which does not require inheritance or classes.
And maybe you have some functions that interact with them but don’t keep them super public so they’re only used by specific modules/store/redux thingy?
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
Of course, but OOP is typically about putting methods on classes, inheritance of behaviour etc.
JS Objects aren’t typically used that way, they tend to be used as pure data containers. At least, that’s how we mostly use them.
Occasionally, we’ll use objects to simplify passing multiple arguments including arrow functions, but I’d say that doesn’t really count unless the arrow function mutates the object it’s a part of.
You’re referring to one subtype of OOP. That may be what most people mean when they say OOP, but that doesn’t make it correct. Object-oriented programming is programming with objects, which does not require inheritance or classes.
With such a broad definition you could call even Haskell an oop language
So you’re arguing that “Object oriented” shouldn’t apply to languages that are oriented around objects?
And maybe you have some functions that interact with them but don’t keep them super public so they’re only used by specific modules/store/redux thingy?