For those that are new here, note: - When the glasses come on; you're about to learn something. - When the glasses come off; a point is about to be hammered in. You're welcome 🙂
I learned C# when MVC5 was still brand new (according to google C# 5 with .Net 4.5), I came from a Java 7 and 8 background. I wasn't a big fan of C# back then, I think likely because of how MVC5 worked overall, but getting used to var and weird concepts like async, delegate, yield, and other such keywords (which I saw being used in codebases at the time). It was only when I started working with C# 7+ that the language clicked for me and async became second nature, it felt like much of what was clear and important to make things work got consolidated slowly over 7 and really took root in 8 with .Net Core which has cemented this language as one of my favourites.
Thank you! This kind of series put things into perspective. Although having coded C# before that, I learned Visual C# 2005, from the Step by Step book in the summer of 2007. It demonstrated boxing and then introduced generics. That version didn't include LINQ. But I barely remember those loops you used to do. Except in other languages.
Excellent, thank you! I've been a software engineer since 1981 and I started writing code in machine language and punching the finished product onto cards. Yikes! I moved to C when the company started running Bell UNIX which at the time was like science fiction. I think that is why I am ALL OVER the newest and latest version of anything. I'll go back and rewrite sections of code if there is a notable improvement in functionality or syntax. Old dog, new tricks: no problem.
For those that are new here, note:
- When the glasses come on; you're about to learn something.
- When the glasses come off; a point is about to be hammered in.
You're welcome 🙂
Lol, historical refactoring / back porting to various dialects? Super nerd content. I love it.
Brilliant, thanks Shawn.
Excellent content. Thanks for explaining the technical and not being judgemental of those of us stuck in framework.
I learned C# when MVC5 was still brand new (according to google C# 5 with .Net 4.5), I came from a Java 7 and 8 background. I wasn't a big fan of C# back then, I think likely because of how MVC5 worked overall, but getting used to var and weird concepts like async, delegate, yield, and other such keywords (which I saw being used in codebases at the time). It was only when I started working with C# 7+ that the language clicked for me and async became second nature, it felt like much of what was clear and important to make things work got consolidated slowly over 7 and really took root in 8 with .Net Core which has cemented this language as one of my favourites.
Thank you! This kind of series put things into perspective. Although having coded C# before that, I learned Visual C# 2005, from the Step by Step book in the summer of 2007. It demonstrated boxing and then introduced generics. That version didn't include LINQ. But I barely remember those loops you used to do. Except in other languages.
Excellent, thank you! I've been a software engineer since 1981 and I started writing code in machine language and punching the finished product onto cards. Yikes! I moved to C when the company started running Bell UNIX which at the time was like science fiction. I think that is why I am ALL OVER the newest and latest version of anything. I'll go back and rewrite sections of code if there is a notable improvement in functionality or syntax. Old dog, new tricks: no problem.
Wow, 1.0 and 2.0 - what a blast from the past. Mixed memories for sure! Thank you!!
You bet!
Fantastic analysis of C#.
Walking down the memory lane 🙂
Thanks for the video! As interesting as always
Incredible content, thank you very much!