i love the fact that mads (who, lets not forget is a C# language designer) said "a bunch of people claim they understand Monads but in reality most don't and if you do understand it, its not for long" Then he says he has understood it many times and then the next day was like "what was it about again?" - How awesome and humbling to hear.
I'm pretty sure that Mads knows exactly what they are and this was slightly tongue in cheek :-) But yes, there's a lot of confusion about them (and the misunderstanding that you need to know what they are to "do" FP).
Coming from a functional background, this talk did a lot to improve my understanding of c sharp. Related it back to what I know and pointed out a bunch of equivalences that I had missed. I don't think I'll ever be a very good c sharp coder but at least it showed me how to read the language. I can relate to having "understood monads many times" lol. Really enjoyed the presentation :)
Compiler language features vs. runtime language features would be a nice thing to have control over. You either set your lang version above what your runtime supports and you have to keep track of runtime features and not use them or you keep it current and can't use any new syntax sugar. Unless this already exists and I've never been able to find it 🙃
This is nice but I just wish F# was more popular and accepted. I am doing debugging on an objected oriented codebase I was not involved with building that has mutable global objects injected all over the place and it's just a nightmare.
When I close my eyes, I see parameterless void methods doing internal mutation. The spaghetti becomes so unbearable, that it makes you wish things were declared explicitly mutable or immutable. But then there are functional patterns to save us, along with Rust for those who like it.
I wish the csharp language team would tackle the null clusterfuck with more effort. The nullable reference types are a neat compiler feature but produces just warnings and enforces nothing. Maybe give us code contracts for method signatures. Like "this param cannot be null" or "this integer must be between 0 and 100" or "will throw this exception when this condition is met". XML documentation is nice (if existing at all) but having a compiler that enforces and safeguards APIs would be way better. Remember ".NET Code Contracts" from Microsoft Research? Pepperidge Farm remembers.
You are very correct. I tried it a bit. Noticed that it doesn't enforce anything. Then I completely disabled it. It would be very very nice if it was a very strict system.
@dasunguy @XtroTheArctic "just warnings" by default. Toss something like dotnet_diagnostic+CS8629+severity = error into an editorconfig and voila, enforcement. (Replacing '+' with period). CS8618 and CS8602 are other relevant ids you may see. Fine-grained control (silent/suggestion/warning/error) is possible, no need for a blanket "all warnings as errors" Edit: Or via VS UI, click lightbulb => Suppress or Configure Issues => Configure Severity ... writes it to editorconfig
@@zhh174 They are trying to get some other features out be proceed with DU - as DU would be built on top of them. Hopefully it would be done sooner rather than later
I am lookin at Zoran Horvat's course on Pluralsight in C# 10 and it seems like records (and record structs) in C# 9 are another important building block in making C# a bit easier to use with functional programming style.
@@kooraiber I believe he was the original leader of the team that developed C#. Before that, he worked for Borland and was the leader of the team that developed Delphi.
The best part about csharp becoming more functional is that people's minds will be more open to Fsharp lol. I made the switch this last year and I am so unbelievably happy it's unreal.
i love the fact that mads (who, lets not forget is a C# language designer) said "a bunch of people claim they understand Monads but in reality most don't and if you do understand it, its not for long" Then he says he has understood it many times and then the next day was like "what was it about again?" - How awesome and humbling to hear.
Yes. Absolutely. A frank and encouraging statement.
I fail to see what the confusion is. A Monad is just a monoid in the category of endofunctors. This is so well easily, simply stated. Easily stated.
@@jewulo Nice. Thats worth an upvote!
@@jewulo ikr!!!
I'm pretty sure that Mads knows exactly what they are and this was slightly tongue in cheek :-) But yes, there's a lot of confusion about them (and the misunderstanding that you need to know what they are to "do" FP).
Coming from a functional background, this talk did a lot to improve my understanding of c sharp. Related it back to what I know and pointed out a bunch of equivalences that I had missed. I don't think I'll ever be a very good c sharp coder but at least it showed me how to read the language. I can relate to having "understood monads many times" lol. Really enjoyed the presentation :)
Compiler language features vs. runtime language features would be a nice thing to have control over.
You either set your lang version above what your runtime supports and you have to keep track of runtime features and not use them or you keep it current and can't use any new syntax sugar.
Unless this already exists and I've never been able to find it 🙃
This is nice but I just wish F# was more popular and accepted. I am doing debugging on an objected oriented codebase I was not involved with building that has mutable global objects injected all over the place and it's just a nightmare.
A typical shit-codebase. I try to avoid them or charge more for it.
When I close my eyes, I see parameterless void methods doing internal mutation.
The spaghetti becomes so unbearable, that it makes you wish things were declared explicitly mutable or immutable.
But then there are functional patterns to save us, along with Rust for those who like it.
I wish the csharp language team would tackle the null clusterfuck with more effort. The nullable reference types are a neat compiler feature but produces just warnings and enforces nothing.
Maybe give us code contracts for method signatures. Like "this param cannot be null" or "this integer must be between 0 and 100" or "will throw this exception when this condition is met".
XML documentation is nice (if existing at all) but having a compiler that enforces and safeguards APIs would be way better. Remember ".NET Code Contracts" from Microsoft Research? Pepperidge Farm remembers.
Pepperidge Farm remembers?
@@rolf8064 a meme
It enforces code to give better intent and meaning
You are very correct. I tried it a bit. Noticed that it doesn't enforce anything. Then I completely disabled it. It would be very very nice if it was a very strict system.
@dasunguy @XtroTheArctic "just warnings" by default. Toss something like dotnet_diagnostic+CS8629+severity = error into an editorconfig and voila, enforcement. (Replacing '+' with period). CS8618 and CS8602 are other relevant ids you may see. Fine-grained control (silent/suggestion/warning/error) is possible, no need for a blanket "all warnings as errors" Edit: Or via VS UI, click lightbulb => Suppress or Configure Issues => Configure Severity ... writes it to editorconfig
Thanks! I really enjoyed this presentation! I'm from the Java world (it's what pays the bills) however in my soul I'd like to work in the C# world
Only thing i want in my life is discriminated unions in c#😂
Yes, please!
I have been dreaming for Discriminated Union
@@obinnaokafor6252 Every year i think the next C# version will surely have but it never does.
@@zhh174 They are trying to get some other features out be proceed with DU - as DU would be built on top of them. Hopefully it would be done sooner rather than later
Type classes and higher kinded types for ever.
Thank you so much for uploading this talk, it is invaluable for me
I am lookin at Zoran Horvat's course on Pluralsight in C# 10 and it seems like records (and record structs) in C# 9 are another important building block in making C# a bit easier to use with functional programming style.
I'm glad Microsoft quickly walked back the C# changes made for complaining VB and C++ programmers. Lead to a much better language.
Brilliant :-)
"When it comes to cloud programming, history is on the side of functional programming. I'm sorry. OOP is not made for that"
Man... that hurts.
Is it possible for Anders Hejlsberg to come back and lead the development of c#?
Why?
@@kooraiber I believe he was the original leader of the team that developed C#. Before that, he worked for Borland and was the leader of the team that developed Delphi.
Fucking amazing :D
Just use F#.
The best part about csharp becoming more functional is that people's minds will be more open to Fsharp lol. I made the switch this last year and I am so unbelievably happy it's unreal.
F# is surprisingly more verbose in some cases - anonymous functions and Seq stuff in particular. Method based linq in C# is just better.
Or both. Put your domain in your f# projects and your infrastructure in your c# projects.
@@gdargdar91 I've had to do this, actually. Efcore doesn't always work as well with fsharp.
@@gdargdar91 Yeah, I use exactly the approach you've described.
how are you?- dear~Wow! really breathtaking footage~:)
Come on guys its 2022, these presentations have to get above Hello World level....
well you know they can never come up with anreal world example that suit their narrative
They have to fit their content into an hour. It's your job to dig deeper.
@@michaelsutherland5848 The dress is red because paper and screwdriver. Its your job to paint the ceiling.
@@chrise202 It's free content. Don't blame them that you're too lazy to learn it.
@@michaelsutherland5848 Lazy to learn what? Hello World? U ok?
most of the code here is just a complete mess