> You also agree that I am not your uncle. Looks like his nephews/nieces are verboten from using the site.
F# for fun and profit: Terms and Conditions
11–20 of 55 posts
Re: F# for fun and profit: Terms and Conditions
#12I 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.
It's all open source now
Re: F# for fun and profit: Terms and Conditions
#13I 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.
Re: F# for fun and profit: Terms and Conditions
#14I 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.
Microsoft will never charge for usage of .NET simply because that's not their business model which relies on mainstream adoption, previously it was to spur sales of Windows Desktop, Servers & their Infrastructure software but now with Azure they're happy for it to have ubiquitous adoption on Linux or Windows servers as well.
Re: F# for fun and profit: Terms and Conditions
#15I 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.
Re: F# for fun and profit: Terms and Conditions
#16Off topic. I highly recommend the book written by the site's author 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…
Direct youtube[1] for those who don't want to click twice :)
Re: F# for fun and profit: Terms and Conditions
#17I 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.
the SDK will always be free, but that's not the business model. the business model is get more people to buy Windows licenses. to that end, they give you a second-class experience on non-Windows (both for development and end-users). eventually you cave and just use Windows and Visual Studio, and rationally so, because you would be at a competitive disadvantage if you did not.
For a long time the F# community criticized Microsoft for their lackluster tooling support in VS where it was treated like a 2nd class citizen, but that's less of an issue now that a lot of devs are developing F# with cross-platform IDEs like VS Code and JetBrains Rider.
Re: F# for fun and profit: Terms and Conditions
#18Re: F# for fun and profit: Terms and Conditions
#19I 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.
the SDK will always be free, but that's not the business model. the business model is get more people to buy Windows licenses. to that end, they give you a second-class experience on non-Windows (both for development and end-users). eventually you cave and just use Windows and Visual Studio, and rationally so, because you would be at a competitive disadvantage if you did not.
Re: F# for fun and profit: Terms and Conditions
#20Off topic. I highly recommend the book written by the site's author 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…
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.