Craig Oates
5 years ago
3 changed files with 16 additions and 0 deletions
@ -0,0 +1,14 @@
|
||||
When I created Console.Waterworks (C.W.), I did not know any F#. I did not have any urge to learn it, either. Because of this, I had very little regard for how C.W. would work in an F# environment. That changed, though, when I stumbled into learning F#... |
||||
|
||||
Having got my feet wet with F#, I started to like it more than C#. One of the things I needed to consider when I began trading in C# for F# was could I still use C.W. in its current state? Well, the answer to that question is yes. So, if you are an F# developer and interested in using C.W., you can. And, if I'm honest, I think C.W. works better when using it with F#. |
||||
|
||||
If you are an F# developer, I am fairly sure you have come across what I call the "F#-Shuffle". The moment you come across some documentation but it's in C# and you need to translate it. I personally found this happened a lot in the early days of me learning F#. That is why I have created a dedicated repository showing how to use C.W. with F#. It is called Brittle Fish and you can find it at the following links: |
||||
|
||||
- [Brittle Fish Repository](https://gitlab.com/craig.oates/Brittle-Fish) |
||||
- [Brittle Fish Wiki](https://gitlab.com/craig.oates/Brittle-Fish/wikis/Home) |
||||
|
||||
The repository has examples for the traditional .Net and .Net Core frameworks. |
||||
|
||||
Unfortunately, the repository can only focus on how to **use** C.W. because it is still a C# code-base. |
||||
|
||||
The reason why it has its own dedicated repository is because I did not want this repository to overwhelm new comers with loads of projects and sprawling wiki articles. On top of that, I get annoyed when I need to traverse through documentation with every compatible language lumped in one place. It is just more stuff to wade through. Anyway, I hope you find my decision to not cross the streams to work in your favour. |
Loading…
Reference in new issue