More like Object-Obsessed.

@fribbledom One of the things that recently struck me as odd is that not all programs fit well to an object oriented approach, but all programs take place in time. I don't know of any language that has an explicit model of time that results in determining the execution model, but a lot where execution is determined by an object model.

@wistahe @fribbledom The classical functional reactive stuff all has time as an important building block.

@tfb @wistahe @fribbledom if there’s any language that bakes in a concept of time (or really, ordered causality) it is clojure

@tfb @wistahe @fribbledom really there’s only two kinds of program that object orientation fits well. games, and guis, and guis fit better with prototypal inheritence than classical inheritence- and games do better with entity / component model

@tfb @wistahe @fribbledom and when i say prototypal, i mean the way newtonscript did it, or the way delegates are used in objective C. javascript has prototypes but there’s nothing out there that uses them the way they’re supposed to be used. neither the browser nor any framework makes effective use of javascript prototypes.

@zensaiyuki @wistahe @fribbledom I sincerely doubt that any language bakes in the arrow of time as deeply as FrTime.

@tfb @wistahe @fribbledom maybe you’re right. i didn’t know it existed. it looks like a library though?

@zensaiyuki @wistahe @fribbledom Racket is a funny beast, but unless you enjoy counting angels on pinheads, I'd just accept any #lang as a language; you can implement Haskell, Coq, Scheme, Prolog, Pascal and more as #lang languages.

@fribbledom classes heirarchies and inheritence are the tools of the Bourgeoisie

@fribbledom oop obsession decreases a lot the pleasure of programming and increase the the developer time. Also it is a big cliff for old programmers, but everything moves in that direction.

@fribbledom Object Oriented means not knowing what your algorithm really is.

@RandomDamage @fribbledom
sometimes it's useful when you don't know what the algorithm should be ahead of time, you only learn it at runtime

@Wolf480pl @fribbledom the problem is that so often you don't have control over the algorithm in use without excess analysis.

It only seems on the surface to be saving programmer time,

@fribbledom I genuinely appreciate all the OOP naysayers in the replies, haha.

@fribbledom OO has suffered the death of a thousand cuts from bad developers using bad OOPLs (C++ I'm looking at you!).

Many technologies suffer at the gate of misuse and silver bullet dreams. OO arose from the ashes of functional programming, and in 30 years will probably do so again.

Shlaer-Mellor did it right, but good abstraction was too hard for the average developer. Fools follow fools.

Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!