The last few years, Functional Programming (FP) has been becoming more and more popular among developers. Speaking of .NET, you can see that a lot of useful features come to C# from F#: LINQ, query expressions, async flow, higher order functions, pattern matching, etc. Why are they so useful? Because they help us focus on business logic instead of thinking about core infrastructure, state changes, concurrency and parallelism issues.
In a lot of programming languages, there are two different concepts for equality: Reference equality (also called Identity) and Value equality. The plan with this article is to convince you that there should only be one equality operator.
There are a lot of new features packaged into C# 7.2. One such feature that piqued our interest because of its simplicity was the
in keyword. It’s one of those things that you can get away with never using in your day to day work but makes complete sense when looking at language design from a high level.
This article shows you four common mistakes C#/.NET developers make when dealing with time. And that’s not all. It also goes through what you should do to avoid them and make your code safer and easier to reason about.
Miguel de Icaza introduces an interactive line editor for .NET applications that he wrote years ago. Of course things like GitHub and Nuget didn't exist back then so sharing something like this was cumbersome. But now it's been pulled out of Mono into it's own library.