I propose a new paradigm:
Objectional programming
Functions don't return
Everything must be done by side effects
Global state mutation is inheritance
Every call is non blocking and spawns a new thread
???
Profit
this post was submitted on 17 Jan 2024
84 points (91.2% liked)
Programming
17318 readers
30 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
Functions don't return... equals goto. Everything must be done by side effects... all variables are global. Global state mutation is inheritance... no grok. Every call is non-blocking and spawns a new thread... atomic bomb for junior software engineers.
??? ... shorting the stock of the company that adopts this.
Profit!
??? … shorting the stock of the company that adopts this.
Screw that I'm going to invest... how do you think Elon Musk got so rich? He did it with sloppy engineering.
To get a first mover advantage, you have to be first. You don't get there by being a perfectionist.
I am currently working on a game for the Atari 2600, and you just gave a good outline of my code. And I love it.
I fundamentally disagree with the idea that these are competing strategies.
Just like walking doesn't really compete, like at all, with flying in an aircraft, Functional and Object Oriented Programming are at their best when you use whichever approach makes sense for a given situation and in any reasonably complex software that means your code should be full of both.
OOP is really good at the high level structure of your software as well as efficiently storing data. FP is really good at business logic and algorithms.
Also, I take issue with the claim that OOP is all about "objects". It's also about classes. In fact I'd argue classes are more important than objects.
The older I get, the more "it depends".
This. Nothing is a silver bullet.
Not even silver bullets.
Object-oriented design is about message-passing; messages are more important than objects. Classes are completely irrelevant -- there's an entire branch of object-oriented language design without classes!
there’s an entire branch of object-oriented language design without classes!
That's not OOP anymore. There's definitely a lot of OOP code out there (especially in the Java world) that goes way too far with inheritance and class structures, and good OOP code relies a lot less on classes - but they are still used and a critical component of the style of programming.
Object-oriented design is about message-passing;
I'd argue that's an implementation detail rather than part of OOP. Also it's rarely used in modern OOP languages because it's just too slow*. Unfortunately when you take it away some patterns are lost, but the trade off is generally worth it.
(* when I used to work in Objective-C, message sending was often slower than all of the rest of my code combined and in tight loops I'd often rewrite my OOP code as procedural C code in order to have acceptable performance. Never need to do that in Swift, which doesn't do messages)
Whatever it may have become in later years, Alan Kay, who is often called "The Father of Object-oriented Programming", outlined the message-passing idea as the main concept he was driving at, originally.
He also says that he probably misnamed it.
Here's a discussion in which the man himself makes a (small) appearance: https://softwareengineering.stackexchange.com/questions/46592/so-what-did-alan-kay-really-mean-by-the-term-object-oriented
JavaScript is an example of how OOP can be done without classes (before they were added to appease Java enthusiasts).
Also, I take issue with the claim that OOP is all about "objects". It's also about classes.
Depending on the language, classes are just objects too. So its still just about objects.
Just like walking doesn't really compete, like at all, with flying in an aircraft, Functional and Object Oriented Programming are at their best when you use whichever approach makes sense for a given situation and in any reasonably complex software that means your code should be full of both.
I'm not really sure sure that's true.
In FP languages like Haskell, you get tools like algebraic data types, typeclasses, and pattern matching.
FP is really opposed to imperative programming, while objects are opposed to algebraic data types.
You can write OO code that's 100% fully functional, and you can write code in Haskell or rust where you barely notice you never once used an object.
I'll just stick them together.
Signed, a Scala programmer.
Yeah, OO and FP aren't really opposed. FP is opposed to imperative programming.
That said, most FP languages give you a slightly different set of tools to use. Algebraic data types and typeclasses are really, really nice.
Honestly, working in Haskell or rust, you don't really miss the fact that you have to jump through hoops to get traditional OO objects. There's just not really many cases where you need them.
Yeah, me too.
Signed, an F# programmer.
Slightly jealous of the F#. Similar set of compelling features minus the JVM.
I'm really glad c# is absorbing more and more functional stuff.
That is nice for when C# is mandated, but it’ll never replace F#
I feel in reality that statement is backwards hehe
If your program functions, it's functional.
Turns out I really love functional programming after all 😹
What if my program is objectionable?
And if it doesn't have objects, then it has no class!
Functions, here, being the key word.
Functions are pure mappings from input to output.
wooosh
I agree with you that if you use functions it's functional.
But many people don't really realize how that contrasts with procedures and procedural code.
I'd be oriented to object
Apparently my brain silently inserted "ing with" into the middle of "program functions" a half dozen times without me noticing.
perchance you were objectively oriented?
Article is pretty lame. Not exactly wrong but doesn't convey a clear understanding.
Agreed, I was hoping for some examples of Functional Programming, since I'm unfamiliar with it.
I got a long form ad for their Haskell book at least!
The free online book learnyouahaskell.com is very good.
Functional is so sexy and I try to use it where I can but I work in a real time environment where the microsecond price of copying immutable data is just too damn high. Still it's useful in places that aren't time critical, especially if the problem is complex.