Why is C# Evolving This Way? @zoran-horvat
Why is C# Evolving This Way?  @zoran-horvat
Uploaded December 2023 | Updated September 2026, 2 weeks ago
C# 12 is here, introducing primary constructors and a few more new features to the language. But this latest version also continues the history of improvements and features added to the C# language and the .NET platform. Do you know that history? Do you know how C# became what it is today?
Two words: Functional programming. That thought underpins most of the evolution during the last twenty years. You don't believe me when I say that functional programming drives C# forward these days? Hear this, then! Hear the list of features added to C# since its version 2.
Generics (including covariance and contravariance, generic constraints, and covariant return types), extension methods and pattern matching, lambda expressions, expression-bodied methods, lambda types, records (and record structs), init-only setters and required properties, nullable references, null-conditional expressions, spans, ranges, expression trees, async streams, async/await.
How will you use these concepts if not in a functional design? But that leaves a screaming question unanswered: Why?
Why should we value functional design as equal to traditional object-oriented design? The reason is that the programming world has been changing through this entire evolutionary process of the C# programming language. We use C# to solve entirely different problems than at the beginning of .NET.
Watch this video and learn the primary motivation behind the latest features of C# and the principal methods of utilizing them in a modern design.

Thank you so much for watching! Please like, comment & share this video as it helps me a ton!! Don't forget to subscribe to my channel for more amazing videos and make sure to hit the bell icon to never miss any updates.🔥❤️

✅🔔 Become a patron ► patreon.com/ZoranHorvat
✅🔔 Subscribe ► youtube.com/channel/UCxsWfh8LCcn55mFB6zGBT1g?sub_confirmation=1
⭐ Learn more from video courses:
Beginning Object-oriented Programming with C# ► codinghelmet.com/go/beginning-oop-with-csharp
⭐ Collections and Generics in C# ► codinghelmet.com/go/collections-and-generics-in-cs
⭐ Making Your C# Code More Object-oriented ► codinghelmet.com/go/making-your-cs-code-more-oo
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
⭐ CONNECT WITH ME 📱👨

🌐Become a patron ► patreon.com/ZoranHorvat
🌐Buy me a Coffee ► ko-fi.com/zoranhorvat
🗳 Pluralsight Courses ► codinghelmet.com/go/pluralsight
📸 Udemy Courses ► codinghelmet.com/go/udemy
📸 Join me on Twitter ► twitter.com/zoranh75
🌐 Read my Articles ► codinghelmet.com/articles
📸 Join me on LinkedIn ► linkedin.com/in/zoran-horvat
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
👨 About Me 👨
Hi, I’m Zoran, I have more than 20 years of experience as a software developer, architect, team lead, and more. I have been programming in C# since its inception in the early 2000s. Since 2017 I have started publishing professional video courses at Pluralsight and Udemy and by this point, there are over 100 hours of the highest-quality videos you can watch on those platforms. On my YouTube channel, you can find shorter video forms focused on clarifying practical issues in coding, design, and architecture of .NET applications.❤️
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
⚡️RIGHT NOTICE:
The Copyright Laws of the United States recognize a “fair use” of copyrighted content. Section 107 of the U.S. Copyright Act states: “Notwithstanding the provisions of sections 106 and 106A, the fair use of a copyrighted work, including such use by reproduction in copies or phono records or by any other means specified by that section, for purposes such as criticism, comment, news reporting, teaching (including multiple copies for classroom use), scholarship, or research, is not an infringement of copyright." This video and our YouTube channel, in general, may contain certain copyrighted works that were not specifically authorized to be used by the copyright holder(s), but which we believe in good faith are protected by federal law and the Fair use doctrine for one or more of the reasons noted above.

#csharp #dotnet #functionalprogramming
Why is C# Evolving This Way?How To Cancel async MethodsThe Pattern That Makes Any Behavior Safe to ChangeBoolean Is Not Your FriendBring Async Superpowers to the Result Type in C#Remove Deep Nesting | Clean CodeThis Explains Why C# 14 Feels So Much Like F#Change Your Mindset to Understand the var KeywordUse Value Objects in EF Core: Fix Anemic Models Without Changing the DatabaseLearn C#: Abstract or Virtual Method, Which Fits Better Here?Have You Got an Aliasing Bug?Are You Afraid of LINQ Aggregate Operator?
Zoran on C# |

Why is C# Evolving This Way?

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER