16
The one thing you cannot do in object-oriented programming but you can in functional
(www.youtube.com)
this post was submitted on 02 Jul 2023
16 points (100.0% liked)
C Sharp
18 readers
1 users here now
A community about the C# programming language
Getting started
Useful resources
- C# documentation
- C# Language Reference
- C# Programming Guide
- C# Coding Conventions
- .NET Framework Reference Source Code
IDEs and code editors
- Visual Studio (Windows/Mac)
- Rider (Windows/Mac/Linux)
- Visual Studio Code (Windows/Mac/Linux)
Tools
Rules
- Rule 1: Follow Lemmy rules
- Rule 2: Be excellent to each other, no hostility towards users for any reason
- Rule 3: No spam of tools/companies/advertisements
Related communities
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Creating new objects would confuse your ORM vs. Always create new objects? Well, you've convinced me.
If you just made copy constructors in the first example, the problem wouldn't have existed. This is wholly contrived, and I feel dumber for having watched it.
Not even saying I like OOP, or that functional isn't usually a better paradigm - but this was the goofiest argument I've seen for it.