The-little-fsharper Alternatives

Similar projects and alternatives to the-little-fsharper

interactive

48 2,732 9.6 C# the-little-fsharper VS interactive

.NET Interactive combines the power of .NET with many other languages to create notebooks, REPLs, and embedded coding experiences. Share code, explore data, write, and learn across your apps in ways you couldn't before.
the-ray-tracer-challenge-fsharp

10 19 4.0 F# the-little-fsharper VS the-ray-tracer-challenge-fsharp

F# implementation of the ray tracer found in The Ray Tracer Challenge by Jamis Buck
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
nand2tetris

9 46 4.4 F# the-little-fsharper VS nand2tetris

Original course HDL solutions, F# implementations for the software stack, and VHDL implementations for the hardware stack for the nand2tetris course and The Elements of Computing Systems book.
ppx_deriving

7 440 7.0 OCaml the-little-fsharper VS ppx_deriving

Type-driven code generation for OCaml

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better the-little-fsharper alternative or higher similarity.

Suggest an alternative to the-little-fsharper

the-little-fsharper reviews and mentions

Posts with mentions or reviews of the-little-fsharper. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-09-07.

F# Libaries and aplication
1 project | /r/fsharp | 16 Oct 2022

Lastly, I recommend maybe taking a look at the book The Little MLer, as it's a great way to become comfortable with discriminated unions and pattern matching on them. Here's some F# annotations for the book: https://github.com/bmitc/the-little-fsharper
Good book to learn F#?
3 projects | /r/fsharp | 7 Sep 2022

Learn functional programming. I'd recommend taking the Programming Languages course, particularly Part A, by Dan Grossman on Coursera. It uses Standard ML (SML) in Part A, which basically shares the same core as F#. Port the examples and your homework solutions from SML to F# to get hands on practice. There is also the book The Little MLer, and I am annotating the book with F# implementations with .NET Interactive notebooks. That book will also hammer home the idea of sum types, pattern matching, and recursion.
OCaml at First Glance
5 projects | news.ycombinator.com | 29 Aug 2022

Yes, please do! Warning: F# will ruin other languages for you. I find it rather painful to work in basically anything else after using F#, with gradients of pain for different languages. Haha.
And that's a good question. I have basically every book written on F#, but I can't say I have ever used them for anything more than reference.
The official docs/guide/reference are actually really good, and I refer to them a lot when using some feature I'm not familiar with: https://docs.microsoft.com/en-us/dotnet/fsharp/what-is-fshar...
F# For Fun and Profit is well-known, but I can't say I use it a lot: https://fsharpforfunandprofit.com/
The same author's (Scott Wlaschin) book is very good: https://pragprog.com/titles/swdddf/domain-modeling-made-func...
As for books, I have always liked:
* Functional Programming Using F# by Hansen and Rischel (might be too simple if you are already comfortable with functional programming and is out of date every now and then with changes to F# that's happened)
* Expert F# 4.0 by Don Syme and others (contains a lot of nice things by the designer of F#
One of the latest books is Stylish F# 6: Crafting Elegant Functional Code for .NET 6 by Kit Eason. I have the first edition but haven't read it.
My personal recommendation is to take the approach of type/domain driven design. That is, I start off every F# module the same:
1. Define my types with discriminated unions, records, type aliases (such as for tuples) or single case discriminated unions. Use classes when necessary but try to prefer the more functional types.
2. Start writing functions against these.
And that's basically it. One thing to recognize with F# is that it mixes OOP rather nicely. Even discriminated unions and records, which are immutable, can have members defined on them, including operator overloading (something F# is pretty good about). They can even implement interfaces and be defined with generic types, which is also nice and powerful.
I have some projects that might of interest, since they're simple enough and illustrate the above process.
https://github.com/bmitc/the-ray-tracer-challenge-fsharp
https://github.com/bmitc/nand2tetris
Lastly, I'd suggest just starting up some projects. You could also take the Programming Languages course on Coursera by Dan Grossman. Part A uses SML, and you could port the examples and homework solutions to F# (I did so when I took the course). I also take books written for other languages and port the code to F#, usually taking a more idiomatic functional style. .NET Interactive notebooks (https://github.com/dotnet/interactive) are a great way to get started. You just need to install the .NET 6 SDK (which gets you F#) and then install the .NET Interactive Notebook extension in VS Code. That's it. There is also the book The Little MLer which gets people comfortable with discriminated unions (sum types), and I used the book and ported the examples to F#. I need to go back and finish that annotation project (https://github.com/bmitc/the-little-fsharper). I'll probably convert the script files to .NET Interactive notebooks if I do.
A note from our sponsor - WorkOS
workos.com | 19 Apr 2024

The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →