|
Nope. Studied a tutorial once. Then went back a few weeks ago to the F# forum and asked myself what I could use F# for, that C# and C++ can't solve. Found no answer....
|
|
|
|
|
I like it, but have no time to use.
|
|
|
|
|
I've recently started teaching myself F# as hobby. Functional programming languages are powerful, elegant and--above all--concise, when applied to the right problems. As a full time .NET developer, I've been curious about the .NET answer to functional programming for a while, and now that it's fully supported for production in VS2010, it seems like a reasonable time to look into it. I'm pleased with what I've seen so far.
Sooner or later, when I've developed a firmer handle on the language, I might campaign within my company to have a very limited portion of our less stable code shifted to F# and to start writing certain pieces of new functionality in F# instead, though I anticipate a lot of perfectly justified resistance to the idea. F# comes with a steeper initial learning curve (unless you're already familiar with the functional paradigm, which most developers I've met aren't), and it either places greater restrictions on who we can hire in the future or it builds a silo around the F# code. Or both.
That being said, once you get past the learning curve, functional languages in general provide a big boost to productivity and a substantial reduction in lines of code, for those coding problems to which they are suited, and as far as I can tell, F# meets the necessary criteria for these benefits to hold. F# is worth looking into if you're trying to parallelize complex code, improve UI responsiveness when users trigger expensive operations that can run in the background, or decompose and/or apply transforms to large, complex chunks of data. Otherwise, unless you have an academic interest, you can probably find a better use for your time.
|
|
|
|
|
I learned to reject it a long time ago when someone on a usenet kept tryin to push F# on everyone but bringing it up at every excuse. Someone shows someone else how to do something in C/C++/C# and this jackass would come up with, "In F# you'd simply have to...." I've always felt that if that was the kind of person who was a propoent of F# then I didn't want to have anything to do with it. Of course I thought rather the same thoughts about C# and .NET up until a couple of years ago.
I'm not a programmer but I play one at the office
|
|
|
|
|
Way to think for yourself.
|
|
|
|
|
Already too many wannabe programming languages available. We don't need another one!
|
|
|
|
|
F# has a completely different goal than the C# based languages.
There are a few articles about it on CP as you may already know so I gues there are individuals using it.
It is a diferent animal and just looking at a few code samples I had a few instant headaches.
There was a time when it would have been fun to delve into it like I did 10-15 years ago with Lisp and Prolog but hell time is not enough these days. You probably already found this:
http://tomasp.net/blog/fsharp-iv-lang.aspx[^]
but for the lazy ones I am posting it again. It is interesting ... what can I say, but it is not going to put bread on my table any time soon.
Cheers.
giuchici
|
|
|
|
|
I haven't used it; but a friend of mine does and likes it a lot...Although I'm not sure what he does with it.
Mike Goldweber
|
|
|
|
|
When I was going through retraining, I looked at the automatically generated F# code when I was working with ASP.NET. Couldn't see the slightest difference from JavaScript. Since I didn't have a book on it, no training oriented with it, and with the complete copy of JS on what I looked at, I lost all interest in it.
I've NEVER seen a job posting for a F# developer.
|
|
|
|
|
So far I am successful in avoiding it in wide circle.
Perhaps I'm just lazy.
|
|
|
|
|
|
Is this a programming question? 
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Is that an "is this a programming question" question? 
|
|
|
|
|
Only for median values of 64. Small increments of 64 or large increments of 64 are not supported.
Software Zen: delete this;
|
|
|
|
|
That's like saying, "We don't sell eggs by the dozen. You have to buy them in packs of 12."
I have nothing more to say.
|
|
|
|
|
"We sell eggs in packs of 6 to 12, in increments of 6."
|
|
|
|
|
Ah yes. Better. 
I have nothing more to say.
|
|
|
|
|
Perhaps they should use:
"We sell eggs in packs of n to double said value, in increments of the former, for n equals 6 (plus or minus zero)."
|
|
|
|
|
AspDotNetDev wrote: "We sell eggs in packs of n to double said value, in increments of the former, for n equals 6 (plus or minus zero)."
...approximately....subject to change without notice...
|
|
|
|
|
42
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
I guess they mean any values of the form "128 + n * 64" between [128 192]!!
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station....
_________________________________________________________
My programs never have bugs, they just develop random features.
|
|
|
|
|
Ahh, published my msdn AND microsoft!
That explains everything.
Obviously, they meant it supports key lengths of 16 and 24 bytes.
|
|
|
|
|
|
Brings back the memories of playing street cricket.
|
|
|
|
|
Yeah but Joe used the :| smiley. I wonder why! 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
