The next major version of C# is C# 8.0. It’s been in the works for quite some time, even as we built and shipped the minor releases C# 7.1, 7.2 and 7.3, and I’m quite excited about the new capabilities it will bring.
The current plan is that C# 8.0 will ship at the same time as .NET Core 3.0. However, the features will start to come alive with the previews of Visual Studio 2019 that we are working on. As those come out and you can start trying them out in earnest, we will provide a whole lot more detail about the individual features. The aim of this post is to give you an overview of what to expect, and a heads-up on where to expect it.
Is engineering an art or a science? Despite years of research and countless books on the subject, our understanding of what quality engineering means is imperfect at best. Many companies, including some here in Silicon Valley, still judge engineering performance by lines of code written and the number of bugs closed. In this talk, Jem Young (@JemYoung) covers some of the big ideas we’ve had in Netflix UI Engineering. But more importantly, what quality engineering is and what we mean when we say “human performance.”
Shared frameworks have been an essential part of .NET Core since 1.0. ASP.NET Core shipped as a shared framework for the first time in 2.1. You may not have noticed if things are working smoothly, but there have been some bumps and ongoing discussion about its design. In this post, I will dive deep into the shared frameworks and talk about some common developer pitfalls.
— David McCarter (@realDotNetDave) November 4, 2018
I thought this was an interesting poll with almost 1000 votes on if your team has moved to .NET Core.