I'm focused on developing and expanding my knowledge and skills. Enjoying new challenges. I'm assuming that there are no stupid questions, there are only silly answers.
Nice post. I started my journey into F# a few days ago, so the comparison between C# and F# is advantageous. I think that we always should use the right tool to achieve our goal. Functional programming is one of the availabilities. I hope I'll get familiar with the new approach to solving problems with FP instead of OO.
Best wishes on your FP journey. The nice thing about F# is you can choose objects when they make sense or when you are not sure how to express something in idiomatically. Most pre-existing .NET libraries use objects, so integrations often must still use some level of object orientation.
Probably the largest benefit you will find is using FP in your core business logic, along with Dependency Rejection. This video has a "testimonial", if you will, on the benefit of this usage. Starting at 17:45. The speaker takes a very pragmatic approach and introduces F# in some parts, but sticks with C# in other parts of the existing system. The talk is overall about architecture, though.
I'm focused on developing and expanding my knowledge and skills. Enjoying new challenges. I'm assuming that there are no stupid questions, there are only silly answers.
Nice post. I started my journey into F# a few days ago, so the comparison between C# and F# is advantageous. I think that we always should use the right tool to achieve our goal. Functional programming is one of the availabilities. I hope I'll get familiar with the new approach to solving problems with FP instead of OO.
Best wishes on your FP journey. The nice thing about F# is you can choose objects when they make sense or when you are not sure how to express something in idiomatically. Most pre-existing .NET libraries use objects, so integrations often must still use some level of object orientation.
Probably the largest benefit you will find is using FP in your core business logic, along with Dependency Rejection. This video has a "testimonial", if you will, on the benefit of this usage. Starting at 17:45. The speaker takes a very pragmatic approach and introduces F# in some parts, but sticks with C# in other parts of the existing system. The talk is overall about architecture, though.
Thanks. I'll take a look on this video.