it's absolutely my favorite language. it's so fantastic, I genuinely have fun every day I get to program in it. It helps me do the simplest thing the quickest, with the most flexibility to pivot if I need to. It's so powerful for basically any task you want it to do. the only limitations are things that are only best done in things like C or Odin or Zig. super high perf stuff is less ergonomic than the normal path, because of CLR limitations and lack of direct memory management.
I think the fact that F# supports mutation is what gives it super powers. My favorite is to write a library with a Functional user facing API with a mutable core for performance. Functional + Procedural = ❤
Yeah! The ability to have a functional programming language, that looks and feels like the ML family of language that supports mutation, OOP, side-effects, amazing module system, AND has proper ecosystem with excellent tooling. Haskell doesn't even have a graphical debugger.
I have discussed this (or similar) with a Microsoft person and it is clear that Microsoft think it is our (F# users) job not theirs. On reflection, I think they are probably right about that.
For me, that I work with c# every day, looks like an awesome language, I read the docs and experimienting with dotnet core with f# , I think the real downside with this kind of lenguages is that depends on other languages, in this case c# , the cognitive charge of having to know c# and also f# it's too hard for beginners or not too advanced programmers like me .. For example if you have to make an web api , then you will have to use asp net core, and know all the related classes, you have to know the BCL of dotnet core itself, and that is with everything, if you have to work with sql, then you need to know how to work with dapper for example, and then translate it to f#, its too hard for the majority of projects.
There are F# implementations of these libraries you mention that are not dependent on C#. Computation Expressions make library development an absolute pleasure.
Really insightful interview! There's always something new to discover in the F# world that makes you wonder how you got along without doing things this way in the first place.
I suppose everyone is asleep and not interested, but I found it fascinating to see Dom Syme highlight the truth about why Microsoft made F# part of its language suite at 15:18 (continuing for 3 minutes). The world might not work as we hope or imagine, but nevertheless things can work out :)
What are your thoughts on the F# programming language?
Please share your thoughts in the comment section.
it's absolutely my favorite language. it's so fantastic, I genuinely have fun every day I get to program in it. It helps me do the simplest thing the quickest, with the most flexibility to pivot if I need to. It's so powerful for basically any task you want it to do. the only limitations are things that are only best done in things like C or Odin or Zig. super high perf stuff is less ergonomic than the normal path, because of CLR limitations and lack of direct memory management.
@Will Ehrendreich Thanks for sharing. How long did it take you to rock the language/programming paradigm?
It's fantastic!
Love it. Wish it was more popular.
I think the fact that F# supports mutation is what gives it super powers. My favorite is to write a library with a Functional user facing API with a mutable core for performance. Functional + Procedural = ❤
Yeah! The ability to have a functional programming language, that looks and feels like the ML family of language that supports mutation, OOP, side-effects, amazing module system, AND has proper ecosystem with excellent tooling. Haskell doesn't even have a graphical debugger.
Great interview and conversation! Thanks for sharing this yall.
Thanks for the help, Jayme.
Yeah, your help and advice have been very valuable
I second the idea for Microsoft to focus on making f# the better python with docs, examples and guides showing the similarities but why it is better.
I have discussed this (or similar) with a Microsoft person and it is clear that Microsoft think it is our (F# users) job not theirs. On reflection, I think they are probably right about that.
Great interview guys.
For me, that I work with c# every day, looks like an awesome language, I read the docs and experimienting with dotnet core with f# , I think the real downside with this kind of lenguages is that depends on other languages, in this case c# , the cognitive charge of having to know c# and also f# it's too hard for beginners or not too advanced programmers like me .. For example if you have to make an web api , then you will have to use asp net core, and know all the related classes, you have to know the BCL of dotnet core itself, and that is with everything, if you have to work with sql, then you need to know how to work with dapper for example, and then translate it to f#, its too hard for the majority of projects.
Yeah one way we can help is making F# videos using these technologies.. You know, something practical
There are F# implementations of these libraries you mention that are not dependent on C#. Computation Expressions make library development an absolute pleasure.
Great discussion, fellas!
Thanks Stephen.
Also, thanks for your mentoring on Azure.
I built an order fulfillment system using Azure.
Really insightful interview! There's always something new to discover in the F# world that makes you wonder how you got along without doing things this way in the first place.
Would be great to talk to Martin Odersky too, he's a very very cool guy actually
Can you introduce us?
Thanks we will reach out to him
@@Bizmonger Sure, I will let him know about you, I hope we will see a wonderful discussion of you three!
I love f#
I suppose everyone is asleep and not interested, but I found it fascinating to see Dom Syme highlight the truth about why Microsoft made F# part of its language suite at 15:18 (continuing for 3 minutes). The world might not work as we hope or imagine, but nevertheless things can work out :)