Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Sep 08, 2010 09:17 PM|LINK
That's a great example.
I haven't touched fluid dynamics etc. for years, but I have a sense of how hard jobs like that can be if the language gets in the way.
I imagine the units of measure feature has been useful in this work.
If you ever publish details of the project, I'd appreciate a mention on this thread, so that I can read it.
On the other question from Johan. I imagine that F# can work well in those categories, in the back end DLL's. For UI creation I imagine many developers may go with the UI design tools of the more established languages like C# and VB.NET.
However in the book Expert F# (I'm using the first edition ISBN-13: 978-1-59059-850-4; Don Syme, Adam Granicz, Antonio Cisternino) there is a chapter entitled "Working with Window Forms and Controls" which illustrates a way to
write form UI's. A refreshing approach! So you are not shut out from writing UI's!
I think the answer depends more on what you actually want to or are inclined to do, and how. If your thinking is purely OO then VB.NET, C# and F# will, arguably, serve you about equally. If you have been bitten by the functional bug and are sometimes thinking
in a different way you could find yourself hooked on F#.
If your choice of language is constrained by the availability of programmers your choice might be different. There seem
not to be a lot of F# programmers around yet, and the financial community is
actively trying to vacuum them up! Longer term, I sincerely hope, that the elegance and power of F# persuades many to become accomplished F# programmers. (That might take a while in a world full of misleading Web 2 noise, inaccuracy and