Live data from Hacker News

F# for fun and profit: Terms and Conditions

fsharpforfunandprofit.com

11–20 of 55 posts

Re: F# for fun and profit: Terms and Conditions

#12
post #10
post #9

I 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

I'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.

Re: F# for fun and profit: Terms and Conditions

#13
post #9

I 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.

If you're still concerned, there's probably nothing they could do at this point.

Re: F# for fun and profit: Terms and Conditions

#14
post #9

I 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.

.NET (SDK/Runtime) has always been free, but it's also been Open Source for several years now whilst F# has basically always been OSS and is stewarded by the non-profit F# Software Foundation.

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

#15
post #9

I 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

#16

Off 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…

On 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

[1]: https://www.youtube.com/watch?v=Nrp_LZ-XGsY

Re: F# for fun and profit: Terms and Conditions

#17
post #15
post #9

I 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.

That's BS, none of the core F# developers have a VS/Windows agenda. F# was one of the first MS products Open Sourced and they were an early adopter of running on Mono back in 2010 in order to run cross-platform. Now they're a supported language on the latest high-performance cross-platform .NET runtime.

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

#19
post #15
post #9

I 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.

windows no, azure yes.

Re: F# for fun and profit: Terms and Conditions

#20

Off 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…

Seconding 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.

Post reply on HN