7 ms·
F# for fun and profit: Terms and Conditions
- sanxiyn 6y agoThis seems to be an ideal terms and conditions I was looking for. I am copying it verbatim to my next website project.
- RcouF1uZ4gsC 6y ago> presenting a talk at the International Conference on Functional Programming entitled “Why Visual Basic DESTROYS Haskell”. I would love to see that talk.
- btschaegg 6y agoDoesn't that vaguely translate to "public execution"?
- neilparikh 6y agoLoosely related: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.72.868&rep=rep1&type=pdf http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.72.... Tthat paper talks about bringing ideas from Haskell to C# and Visual Basic (!).
- bluebean 6y ago> You also agree that I am not your uncle. Looks like his nephews/nieces are verboten from using the site.
- recursive 6y agoReads to me like a jab at "Uncle Bob"
- deleted 6y ago[deleted]
- red2awn 6y agoI like that the terms and conditions page has a comment section beneath it.
- sum_numpty 6y agoSuper neat, right? Wish this was more widely adopted. But disincentives, I guess ...
- Barrin92 6y agoI only used F# on the side for a few casual projects but I'd really love for it to gain much more traction. Just like Clojure feels to me like a great pragmatic language on top of the JVM, F# feels like Ocaml on top of a really strong ecosystem.
- mumblemumble 6y agoIt often gets compared to Scala, but, personally, I genuinely prefer F#. It has that ML feel, but without quite the same "I'm trying to be Haskell but I'm trapped inside a (relatively) weakly typed object-imperative universe" identity crisis. It also does some nice things from a pragmatic perspective. It's true that computation expressions are nerfed monads, but they're done in a way that makes unfamiliar code easier to read. I find the tradeoff to be a net gain for the teamwork story. And, while pattern matching is everywhere these days, I still think F# wears it best.
- jumanjisama 6y agoOff topic. I highly recommend the book written by the site's author https://pragprog.com/titles/swdddf/domain-modeling-made-functional/ https://pragprog.com/titles/swdddf/domain-modeling-made-func... Although it may look like just Domain Driven Design (DDD) and F# from the title. I think I've learnt a lot more from it. It changed the way I approached a problem and I somehow keep coming back to the book to get a refresher of the teachings in it. I suspect it is due to the influence of F# and functional paradigms that is also being shared in the book.
- __henil 6y agoOn the same note, I recently shared a link[0] to his great beginner talk on functional programming languages. This was by far the best introduction to monoid, monads and few other functional programming terms. Direct youtube[1] for those who don't want to click twice :) [0]: https://news.ycombinator.com/item?id=25571001 https://news.ycombinator.com/item?id=25571001 [1]: https://www.youtube.com/watch?v=Nrp_LZ-XGsY https://www.youtube.com/watch?v=Nrp_LZ-XGsY
- goostavos 6y agoSeconding this! It's one of the very few tech books I've read cover to cover more than once. I similarly find myself revisiting individual pieces of it often. It completely changed the way I thought about the role of type systems -- and I don't even mean in terms of monads, functors, or any other higher level category theoretic stuff. I mean just the day-to-day business coding idea of representing more of your domain directly in the type system. I now find that pencil and paper is the best programming tool. It's massively easier to iterate on types and arrows between them than it is to pluck away against and refactor actual implementations.
- rayxi271828 6y agoWould you mind sharing other tech books you've read cover-to-cover more than once?
- BoiledCabbage 6y agoEven if you never plan to touch F#, I found it a really insightful approach for modeling domain problems - and capturing the rules of the system you are trying to model in your code and data types. Really well done, and such a easy read as well. It's not that it's revolutionary, but it one of those things that once you read it both seems obvious and also makes you wonder why we do things any other way.
- ilaksh 6y agoI really like F# but am concerned there might be some kind of gotcha with using it in a commercial project. Like somehow Microsoft might decide to require payment for .NET or something.
- gdsdfe 6y agoIt's all open source now
- oooooooooooow 6y agoI'm fairly sure fsharp has always been open source, or at least it was open sourced very early. Somewhat pioneering of MS approach to licensing basic development tools.
- swiley 6y agoYou're still going to have to download a binary from Microsoft. This is the nature of self hosting compilers. It would be nice if there were an alternative implementation (say, a gcc or llvm front end) that you could bootstrap it from but that's not how it is right now. This creeped me out just enough that I haven't played with it. Microsoft has changed a lot but downloading Linux binaries from them is still just a bit too much.
- mythz 6y agoIf you're concerned, why can't you just build F# from its OSS Repo with their build.cmd or build.sh scripts? https://github.com/dotnet/fsharp#contributing https://github.com/dotnet/fsharp#contributing They even have a Visual Studio Online quickstart which provisions the build environment with all necessary dependencies: https://github.com/dotnet/fsharp#visual-studio-online-quickstart https://github.com/dotnet/fsharp#visual-studio-online-quicks... Where the build environment wouldn't be running on your machine.
- Gaelan 6y agoThe F# compiler seems to be written in F#. Therefore, you need to already have an F# compiler to build it. That GitHub repo mentions that "You will also need the latest .NET 5 SDK", which looks like it includes F#. (Presumably, when the language was first written, there existed a compiler written in some other language. However, that compiler is almost certainly not maintained anymore, so it wouldn't be able to compile today's compiler, which probably uses language features added since then.)
- circuit_ 6y agolol at the comments
- mikaeluman 6y agoScott W has a great approach to domain modeling. While he covers many topics, and almost all of F#, I think the way he uses the language to model a domain is what stands out as something that could really be of use in many real world applications. Just looking at my own pet project of yatzy that I implemented in F# in a day, I used discriminated unions and enums to model all of it.
- notretarded 6y agoWhat are some real world uses for this that people have used outside of their sandpit i.e. at work? I regularly see functional programming get voted to the top, but never any practical applications of such.
- nojito 6y agoJet.com is a great example. https://youtu.be/FskIb9SariI?t=409 https://youtu.be/FskIb9SariI?t=409
- kmc059000 6y agoExcept it doesn't really exist anymore. Perhaps F# lives on within Walmart though. https://www.cnbc.com/2020/05/19/walmart-winds-down-jetcom-four-years-after-3point3-billion-acquisition.html https://www.cnbc.com/2020/05/19/walmart-winds-down-jetcom-fo...
- nojito 6y agoThe brand doesn't, but the tech is all over Walmart
- KurtMueller 6y agoIf you're seeing F# in a project at work (and in production), isn't that real world use? Anyway, I just sat in a Mathematical Planning seminar with a guy from Quicken Loans who uses F# in production at work (Matthew Crews). He is also an author behind the Flips F# library. A quick list of F# libs for real world, everyday uses: * Pulumi / Farmer - code as infrastructure * FAKE - build tool * Fable - javascript transpiler * Feliz - react elements * FSharp.Data - parsing csvs, html pages * Http.fs - making http calls I've been using F# to parse CSVs at work and using result types and a ton of F# active patterns.
- jpcooper 6y agoAny migrants from Haskell to F# who have used it for larger projects and can compare the two? I’ve used Haskell on and off for a number of years for a number of small projects, and I’m considering moving to F# for better IDE and debugger support, and I’m wondering whether there are any downsides in comparison to Haskell which I should consider. Any result-based advice would be appreciated.
- goto11 6y agoFor larger F# projects you will probably use a bunch of .net libraries. It is of course an advantage of F# that you can, but it also makes the language feel like an uneasy hybrid. For example F# functions are called with a different syntax than .net functions/methods. Haskell feels much more consistent. I prefer F# for larger projects because it makes a bunch of pragmatic compromises. IMHO languages which a singular vision (Scheme, Smalltalk, Haskell) are great for learning and expanding your mind, but when it comes to larger real-world projects, dogmatism just gets in the way.
- jpcooper 6y agoThanks for the tips.
- f0rgot 6y agoI have a ton of respect for Scott. Such a clear, concise, and unpretentious teacher. I've learned a good deal from this man in a very small amount of time.
- alexdean 6y agoI chortled when I saw the health warning against railway-oriented programming. Reading that post deeply influenced (and continues to influence) the architecture of Snowplow (https://github.com/snowplow/snowplow https://github.com/snowplow/snowplow) and I titled a chapter of Event Streams in Action 'Railway-Oriented Processing' (https://www.manning.com/books/event-streams-in-action https://www.manning.com/books/event-streams-in-action). Thanks Scott.
- ablekh 6y agoTwo questions for those with significant experience developing in F#: 1. Have you tried using JetBrain's Rider IDE for that and, if so, how deficient your experience was when compared to using Rider for C# development? If, alternatively, you have used VS Code for F# development, how much support is there - generally and when compared to Rider - in terms of both language features and external frameworks/libraries (Fable, etc.)? 2. Could you quantify both quality and productivity gains from developing a complex system in F# versus developing it in C#?
- saulr 6y agoI have several years of full-time F# experience and I’ve also made some contributions to the F# support for Rider. 1. As part of my job I flip between C# and F# often and with each new release of Rider the IDE-support gap between them is closing. Obviously C# has many more years of attention and work on its tooling, but there are very few things I yearn for when editing F# code nowadays. I also find Rider far better to use than VS Code for F#, simply because I’m so comfortable with JetBrains’s IDEs now. 2. Any time I have to model anything remotely complex in C# I always wish I was doing it in F# instead. Features like discriminated unions, exhaustive pattern matching and immutability-by-default immediately spring to mind.
- ablekh 6y agoI appreciate you sharing your experiences. (Though your comment on #2 is very helpful as well, I was specifically interested in quantified estimates of differences in resulting system quality and developer productivity, if at all possible.) BTW, do you use any external frameworks? Would you prefer to use something like Fable over Blazor for Web development or vice versa? Why?
- bern4444 6y agoScott is able to convey ideas and subject matter so well, his site and his videos are incredibly insightful even if you never write a line of F#. As a separate note, I find F# to be a breath of fresh air as a language, I only wish it was more widely used professionally. The list of companies using it is few and far between similar to when people ask where lisp or scheme is used in the real world and everyone references Jane Street and Hacker News as the only two examples. I've had fun writing a little bit of F# on my own for some personal projects using Fable to transpile it to Javascript. It can be difficult to get good with a language when you don't use it profesionally 8 hours a day 5 days a week. Hard to convince a manager to allow for a new language in a project (it was difficult enought to get approval for TypeScript on top of Javascript to begin with).
- saulr 6y agoThe companies using F# are definitely few and far between, but G-Research in London are hiring an F# developer at the moment. If this sounds like something you’d be interested in, please reach out to me at: im (at) saul.re