21–30 of 131 posts
Thank you for the part in round brackets, I wish more submissions were formed in this way.
Wouldn't have even clicked if not for the brackets. My mind jumped to the crappy game https://en.wikipedia.org/wiki/Fable_III
Earlier quoted context omitted.
Yep. We’re using F# React on the front-end, Giraffe on the back-end. DustyTables for Data Access. It’s great - can recommend.
what about efcore does it work in f#? or is it bad practice to use mutable code/objects in f#? i do not want to go back to plain sql...
What sometimes leads to problems is F#’s record and discriminated union types.
Not sure how they are handled by EF Core.
Going back to plain SQL is just great. You know exactly what SQL gets executed. No Magic.
With DustyTables it’s also not too much boilerplate.
Earlier quoted context omitted.
Wouldn't have even clicked if not for the brackets. My mind jumped to the crappy game https://en.wikipedia.org/wiki/Fable_III
Huh, today I learned "parenthesis" are called "round brackets" in UK
I'm sure someone must use it but it's not at all common
How does Fable 3 stack up against ReScript or Scala.js? Is the only difference the ecosystem around the toolchains?
Earlier quoted context omitted.
Yep. We’re using F# React on the front-end, Giraffe on the back-end. DustyTables for Data Access. It’s great - can recommend.
Is the market for F# picking up now in 2020? At my current job we're not using F# but I'd like to eventually move to a place that does. I am learning on my own at the moment and am wondering how open the potential hiring companies would be with novices in F# who otherwise have good experience in other languages.
If you want to work in F# come up with your own OSS projects or champion it at work.
Earlier quoted context omitted.
what about efcore does it work in f#? or is it bad practice to use mutable code/objects in f#? i do not want to go back to plain sql...
It’s a .Net library so it works (or should work) with F#. What sometimes leads to problems is F#’s record and discriminated union types. Not sure how they are handled by EF Core. Going back to plain SQL is just great. You know exactly what SQL gets executed. No Magic. With DustyTables it’s also not too much boilerplate.
Earlier quoted context omitted.
It’s a .Net library so it works (or should work) with F#. What sometimes leads to problems is F#’s record and discriminated union types. Not sure how they are handled by EF Core. Going back to plain SQL is just great. You know exactly what SQL gets executed. No Magic. With DustyTables it’s also not too much boilerplate.
Design-time support is still via a non-released package. So you'll write models/etc in C# and use EF from F#. There are ways to get design-time constructs working in F#, but it's not plug-and-play like from the C# side.
Earlier quoted context omitted.
Huh, today I learned "parenthesis" are called "round brackets" in UK
I have never ever heard anyone call them that in the UK, they're either brackets or parenthesis to anyone I've ever spoken to - from scientists, to builders, my grandparents all said brackets (Including the one is almost illiterate) I'm sure someone must use it but it's not at all common