C Sharp

1532 readers

1 users here now

A community about the C# programming language

Getting started

Useful resources

IDEs and code editors

Visual Studio (Windows/Mac)
Rider (Windows/Mac/Linux)
Visual Studio Code (Windows/Mac/Linux)

Tools

Decompilers: ILSpy, dotPeek
Scratchpad: LINQPad
Online playground and IL viewer: SharpLab

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

c/dotnet

founded 1 year ago

MODERATORS

Ategon

nibblebit

Spyros

The one thing you cannot do in object-oriented programming but you can in functional (www.youtube.com)

submitted 1 year ago by canpolat to c/csharp

7 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Fordiman 4 points 1 year ago

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.